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
Removed service worker #12974
Removed service worker #12974
Conversation
|
I've got some rspec test failures. I can look at those later tonight unless someone wants to jump on that. |
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.
Haven't had a chance to test it yet but left an initial question inline
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.
Tested locally in chrome and successfully removed an already installed service worker. 👍🏻
|
@nickytonline does this commit help with seo problem in #9509? |
@liflovs , it should but I think there may be some additional dead code to remove based on @benhalpern's comment #9509 (comment). Going to out this back into draft mode to validate this next week. |
|
Tested with Chromium Edge on Windows, works as expected here too 👍 |
|
Just a heads up that I restarted the failed build Travis but maybe I didn't need to 😅 |
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.
🚀
What type of PR is this? (check all applicable)
Description
This removes all of our service worker functionality with a self-destructing service worker which appears to be the best approach for unregistering a service worker. See https://github.com/NekR/self-destroying-sw#how-to-use.
Related Tickets & Documents
#12899
#12631
#12000
#11606
#11533
#11488
#11270
#10293
#10173
#9657
#9642
#9509
#9254
#9228
#8729
#7339
#7081
#6497
QA Instructions, Screenshots, Recordings
Test this in Chrome, Firefox, and Safari. Note in Safari, there may be no service worker registered due to the work done with the service-companion.js file. In that case, ensure that no errors are thrown in the console of the web dev tools in Safari.
Chrome
Firefox
Safari
Chrome
Firefox
Safari
UI accessibility concerns?
N/A this is front-end infrastructure
Added tests?
[Forem core team only] How will this change be communicated?
Will this PR introduce a change that impacts Forem members or creators, the
development process, or any of our internal teams? If so, please note how you
will share this change with the people who need to know about it.
Admin Guide, or
Storybook (for Crayons components)
or in a forem.dev post
replace this line with details on why this change doesn't need to be
shared
[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?