You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The app-init.js service worker should only stay alive if the page dapp provider is connected. Currently, the service worker is kept alive as long as the page is open.
digiwand
changed the title
[MV3]: Service Worker should terminate if dapp provider is not connected
MV3: Service Worker should terminate if dapp provider is not connected
Sep 12, 2022
digiwand
changed the title
MV3: Service Worker should terminate if dapp provider is not connected
MV3: Service Worker should be kept active only when accounts are connected to the dapp
Sep 26, 2022
digiwand
changed the title
MV3: Service Worker should be kept active only when accounts are connected to the dapp
MV3: Service Worker should be kept active only after the dapp has been interacted with
Oct 3, 2022
Describe the bug
The app-init.js service worker should only stay alive if the page dapp provider is connected. Currently, the service worker is kept alive as long as the page is open.
See #15494 (comment) for more details.
Criteria:
Note that support to connect Service Worker after it has been inactive will be handled in this PR (WIP, Needs update):
#15986
Steps to reproduce
https://
orhttp://
pagesapp-init.js
service worker is not running. If it is still running, terminate the service worker.https://
orhttp://
pageError messages or log output
No response
Version
10.18.4
Build type
No response
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: