Ctrl+Click / Cmd+Click also opens in a new tab.
As someone involved in the WebExtensions Community Group who has been (slowly) trying to figure out what, if anything, we should do at the platform level around these use cases, I appreciate you raising and repeating…
Oh, this is interesting! I assume most of the heavy lifting to identify and filter content is being performed by the content script. In practice have you see any issues with models accessing page content before the…
Do you mean Firefox on iOS? If so, that would require the firefox-ios project to adopt BrowserEngineKit, which is relatively new. Firefox for iOS WebExtension support is being tracked in…
Also pretty easy with Firefox's new profile manager https://support.mozilla.org/kb/profile-management
Just took a quick glance at your extension and observed that it's currently using the "debugger" permission. What features necessitated using this API rather than leveraging content scripts and less invasive…
Simeon from the Firefox Add-ons team here. Sorry about the rocky experience. I realize this is a bit late for your situation, but earlier this year the source code submission docs were updated with information about the…
Asking as a browser contributor, what do you feel is missing from MV3?
I was about to say "concurrent writes shouldn't be a problem because localStorage is synchronous and JS is single-threaded," but then I started thinking about multiple tabs, WebWorkers, and multi-process browsers and…
Would love to hear your thoughts on how to improve it ;)
Can you share more about what you find frustrating or confusing about this process?
Chrome extensions are published on Chrome Web Store (https://chromewebstore.google.com), not on Google Play.
I don't know exactly what the the person you're replying to had in mind, but support for different parts of the manifest varies (especially in Manifest V3). While it's possible to write a single manifest that works in…
To my knowledge no browser supports transferring an extension's user base from one extension to another. If you want your users to switch, the only think you can do is show them a link of where to get the new extension…
Both CWS (Chrome) and AMO (Firefox) supports this. It's part of Chrome's One Stop Support[1] form and Forefox's developer hub UI. At the moment I don't believe any browser has features that notify end users of ownership…
> The extension ID is derived from a private key that the developer uploads with the first upload to the app store While what you described is possible, this process isn't required or the typical way an extension ID is…
Sounds like literal rent seeking behavior.
> If the idea is that these DNR rules require non-fast-trackable thorough reviews, but dynamically updating them will bypass those thorough reviews, than I am at a lost to understand the logic of treating them as…
No one does at the moment. The deprecation is on hold, but Chrome has stated that they "will provide at least 6 months between a timeline announcement and any experiments deprecating MV2 features":…
> I wonder if the main obstacle to (actual) cross-browser extensions isn't so much technical but rather political. Normally when browser folk talk about "cross-browser extensions," we're not focusing on the…
> the extension APIs are standardised enough that this is actually possible a lot of the time A bit off topic, but as a co-chair of the WebExtensions Community Group[1] (WECG) I'm a bit touchy about the calling…
> The biggest problem I found is that Chrome Manifest V3 requires background.service_worker (they removed background.scripts), while Firefox Manifest V3 requires background.scripts (they never implemented…
This was a mistake and has been corrected.
> Absent security issues, what's the value of the last N releases of Chrome? How far do you have to go to get something of value that changed? IMO something of value changes with every release. For example, in the most…
A couple hours ago I added a comment to the bug to describe our current plans[1]. TL:DR; you'll be able to use webRequest.onAuthRequired in MV3. [1]: https://bugs.chromium.org/p/chromium/issues/detail?id=113549...
Ctrl+Click / Cmd+Click also opens in a new tab.
As someone involved in the WebExtensions Community Group who has been (slowly) trying to figure out what, if anything, we should do at the platform level around these use cases, I appreciate you raising and repeating…
Oh, this is interesting! I assume most of the heavy lifting to identify and filter content is being performed by the content script. In practice have you see any issues with models accessing page content before the…
Do you mean Firefox on iOS? If so, that would require the firefox-ios project to adopt BrowserEngineKit, which is relatively new. Firefox for iOS WebExtension support is being tracked in…
Also pretty easy with Firefox's new profile manager https://support.mozilla.org/kb/profile-management
Just took a quick glance at your extension and observed that it's currently using the "debugger" permission. What features necessitated using this API rather than leveraging content scripts and less invasive…
Simeon from the Firefox Add-ons team here. Sorry about the rocky experience. I realize this is a bit late for your situation, but earlier this year the source code submission docs were updated with information about the…
Asking as a browser contributor, what do you feel is missing from MV3?
I was about to say "concurrent writes shouldn't be a problem because localStorage is synchronous and JS is single-threaded," but then I started thinking about multiple tabs, WebWorkers, and multi-process browsers and…
Would love to hear your thoughts on how to improve it ;)
Can you share more about what you find frustrating or confusing about this process?
Chrome extensions are published on Chrome Web Store (https://chromewebstore.google.com), not on Google Play.
I don't know exactly what the the person you're replying to had in mind, but support for different parts of the manifest varies (especially in Manifest V3). While it's possible to write a single manifest that works in…
To my knowledge no browser supports transferring an extension's user base from one extension to another. If you want your users to switch, the only think you can do is show them a link of where to get the new extension…
Both CWS (Chrome) and AMO (Firefox) supports this. It's part of Chrome's One Stop Support[1] form and Forefox's developer hub UI. At the moment I don't believe any browser has features that notify end users of ownership…
> The extension ID is derived from a private key that the developer uploads with the first upload to the app store While what you described is possible, this process isn't required or the typical way an extension ID is…
Sounds like literal rent seeking behavior.
> If the idea is that these DNR rules require non-fast-trackable thorough reviews, but dynamically updating them will bypass those thorough reviews, than I am at a lost to understand the logic of treating them as…
No one does at the moment. The deprecation is on hold, but Chrome has stated that they "will provide at least 6 months between a timeline announcement and any experiments deprecating MV2 features":…
> I wonder if the main obstacle to (actual) cross-browser extensions isn't so much technical but rather political. Normally when browser folk talk about "cross-browser extensions," we're not focusing on the…
> the extension APIs are standardised enough that this is actually possible a lot of the time A bit off topic, but as a co-chair of the WebExtensions Community Group[1] (WECG) I'm a bit touchy about the calling…
> The biggest problem I found is that Chrome Manifest V3 requires background.service_worker (they removed background.scripts), while Firefox Manifest V3 requires background.scripts (they never implemented…
This was a mistake and has been corrected.
> Absent security issues, what's the value of the last N releases of Chrome? How far do you have to go to get something of value that changed? IMO something of value changes with every release. For example, in the most…
A couple hours ago I added a comment to the bug to describe our current plans[1]. TL:DR; you'll be able to use webRequest.onAuthRequired in MV3. [1]: https://bugs.chromium.org/p/chromium/issues/detail?id=113549...