-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update Manifest to V3, include mixed-mode tudor crown icons #186
Conversation
41f7a2b
to
ae88148
Compare
Co-authored-by: Kashif Atcha <[email protected]> Co-authored-by: Jon Kirwan <[email protected]> Co-authored-by: Keith Lawrence <[email protected]>
Co-authored-by: Kashif Atcha <[email protected]> Co-authored-by: Jon Kirwan <[email protected]> Co-authored-by: Keith Lawrence <[email protected]>
- New Chrome APIs mean we can't detect dark mode in a service worker, so remove dark mode versions and add mixed-mode-safe icons of the Tudor crown Co-authored-by: Kashif Atcha <[email protected]> Co-authored-by: Jon Kirwan <[email protected]> Co-authored-by: Keith Lawrence <[email protected]>
- A/B testing component temporarily disabled to allow deploy Co-authored-by: Kashif Atcha <[email protected]> Co-authored-by: Jon Kirwan <[email protected]> Co-authored-by: Keith Lawrence <[email protected]>
Co-authored-by: Kashif Atcha <[email protected]> Co-authored-by: Jon Kirwan <[email protected]> Co-authored-by: Keith Lawrence <[email protected]>
Co-authored-by: Kashif Atcha <[email protected]> Co-authored-by: Jon Kirwan <[email protected]> Co-authored-by: Keith Lawrence <[email protected]>
- Temporarily disable A/B testing related code - chrome.tabe.executeScript -> chrome.scripting.executeScript (calling functions now have to be async) - Remove reliance on component states that might not be available in async code - explicit location parts in re-render popup code Co-authored-by: Kashif Atcha <[email protected]> Co-authored-by: Jon Kirwan <[email protected]> Co-authored-by: Keith Lawrence <[email protected]>
ae88148
to
1cbfa0a
Compare
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.
NIce work removing this!
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.
Nice work on this update!
I've checked the code and referred to the Migration guide and all looks good to me - https://developer.chrome.com/docs/extensions/develop/migrate
I've also tested the changes using the unpacked chrome extensions in my browser and all the functionality still works as expected, knowing that the functionality for AB tests will be added back in the future.
@KludgeKML are there any plans to add the ab test toggle back into the chrome extension? |
In its current state, and presumably since the [Manifest V3 migration](#186), the extension doesn't work on Firefox. However, it can be made fully functional with a small change When loading the extension in Firefox, the following is reported ``` There was an error during the temporary add-on installation. Error details background.service_worker is currently disabled ``` Firefox doesn't currently support `background.service_worker` in Manifest V3: https://bugzilla.mozilla.org/show_bug.cgi?id=1573659. This property was added when migrating to V3: #186 If you remove this section from the manifest, it will work on V3. The only caveat is that the icon won't change when on a GOV.UK page I also tried changing `service_worker` to `scripts` and using an array per [this suggestion](mozilla/web-ext#2532 (comment)), which also makes the extension functional, but doesn't make the icon-changing script work. I suspect the `icon.js` code would need updating for cross-browser support. Other suggestions later in that thread might be worth exploring, but it might make more sense to hold off until Firefox adds proper support if the user base is low
In its current state, and presumably since the [Manifest V3 migration](#186), the extension doesn't work on Firefox. However, it can be made fully functional with a small change When loading the extension in Firefox, the following is reported ``` There was an error during the temporary add-on installation. Error details background.service_worker is currently disabled ``` Firefox doesn't currently support `background.service_worker` in Manifest V3: https://bugzilla.mozilla.org/show_bug.cgi?id=1573659. This property was added when migrating to V3: #186 If you remove this section from the manifest, it will work on V3. The only caveat is that the icon won't change when on a GOV.UK page I also tried changing `service_worker` to `scripts` and using an array per [this suggestion](mozilla/web-ext#2532 (comment)), which also makes the extension functional, but doesn't make the icon-changing script work. I suspect the `icon.js` code would need updating for cross-browser support. Other suggestions later in that thread might be worth exploring, but it might make more sense to hold off until Firefox adds proper support if the user base is low
Compromise release version to cope with the fact that we need to update the crown logo and V2 manifests can no longer be deployed to Chrome Web Store.
https://trello.com/c/liGfGsga/2174-migrate-to-a-service-worker