fix: implement ping-pong mechanism to keep service worker alive #1956
+29
−22
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The service worker was becoming inactive when browser tabs lost focus. Implemented a more reliable ping-pong mechanism that sends regular ping messages from all UI contexts to the background service, preventing the browser from considering the service worker inactive.
mkazlauskas
force-pushed
the
fix/keep-sw-alive
branch
from
236696e to
aae4e45
Compare
|
Allure Report
processReports: ✅ test report for aae4e451
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The service worker was becoming inactive when browser tabs lost focus. Implemented a more reliable ping-pong mechanism that sends regular ping messages from all UI contexts to the background service, preventing the browser from considering the service worker inactive.
Checklist
Proposed solution
Explain how does this PR solves the problem stated in JIRA ticket.
You can also enumerate different alternatives considered while approaching this task.
Testing
Untested
Screenshots
Attach screenshots here if implementation involves some UI changes