Update Chrome incompatibilities page for browser namespace support - #44959
Conversation
Remove outdated information on `browser` namespace support and promise
support. This page could do with a lot of additional work, but scoping
this change as strictly as possible to reduce creep. Similarly, another
article ("Cross-platform extension coding hurdles") could do with
further updates but making only the minimum required changes and will
update that further in a second PR.
github-actions
Bot
added
Content:WebExt
|
@Rob--W having seen this, I realized that I missed an update to the information about namespace and promise support on this page. Please let me know if you prefer approach (moving this content to historical section) or providing version details similar to https://github.com/mozilla/extension-workshop/pull/2401/changes#diff-22d746d8296b719d8e0e7ca6fdd36233ee308d130085e8f24d793892fa0576f6R32 |
Rob--W
left a comment
Rob--W
left a comment
There was a problem hiding this comment.
I like the concluding historical information section, as well as the preservation of the same header title so that permalinks continue to point there.
But I also think that it removes a bit too much. The historical state of support for callbacks vs promises is relevant, as well as the link to the polyfill (whose readme I had already updated, by the way). These two are needed for people inheriting projects to understand why code bases have historical bagage.
|
There is also PR #44951 touching some content around the same topic. |
|
I've updated this to restore the mention of callbacks and the polyfill. Could you take another look? |
…ties/index.md Co-authored-by: rebloor <git@sherpa.co.nz>
4 participants
Description
Remove outdated information on
browsernamespace support and promise support. This page could do with a lot of additional work, but scoping this change as strictly as possible to reduce creep. Similarly, another article ("Cross-platform extension coding hurdles") could do with further updates but making only the minimum required changes and will update that further in a second PR.Motivation
We've made a lot of progress in the last few years which would be nice to deprecate. The
chromenamespace has been stable for several versions.Additional details
https://developer.chrome.com/docs/extensions/whats-new#chrome_148_the_browser_namespace
Related issues and pull requests
N/A