-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MV3: Update service worker restart logic and keep-alive logic for dapp support #16075
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
…:MetaMask/metamask-extension into mv3-dapp-sendMessage-after-SW-inactivity
…:MetaMask/metamask-extension into mv3-dapp-sendMessage-after-SW-inactivity
Builds ready [c6f042e]
Page Load Metrics (2343 ± 109 ms)
|
Builds ready [eff5234]
Page Load Metrics (2343 ± 143 ms)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM except for minor feedbacks.
Builds ready [db28cf8]
Page Load Metrics (2209 ± 125 ms)
highlights:storybook
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great documentation, @digiwand Thank you! LGTM
Explanation
This PR:
Details of Implementation:
Other important notes regarding this PR:
Could not establish connection. Receiving end does not exist
#16434Side note:
While I was out for 2 weeks, @jpuri assisted by adding some commits. I have returned with more commits.
More Information
Fixes: #15986
Fixes: #15802
Screenshots/Screencaps
Manual Testing Steps
Test Service Worker is not kept alive on non-dapp pages:
Test Service Worker is kept alive on dapp pages:
Test Service Worker can be reactivated after inactivity:
(note: There might be a delay to re-activate. @jpuri is working on a task to fix this. More details to come)
Pre-Merge Checklist
+ If there are functional changes: