Mozilla Outlines Plan For Manifest V3 Extensions API – Slashdot | xxxMozilla Outlines Plan For Manifest V3 Extensions API – Slashdot – xxx
菜单

Mozilla Outlines Plan For Manifest V3 Extensions API – Slashdot

七月 31, 2019 - MorningStar

Slashdot is powered by your submissions, so send in your scoop

 


Forgot your password?
Close

binspamdupenotthebestofftopicslownewsdaystalestupid freshfunnyinsightfulinterestingmaybe offtopicflamebaittrollredundantoverrated insightfulinterestinginformativefunnyunderrated descriptive typodupeerror

Check out Slashdot on LinkedIn & Minds! | Migrate from GitHub to SourceForge quickly and easily with this tool. Check out all of SourceForge’s improvements.

×

115103104 story

Mozilla Outlines Plan For Manifest V3 Extensions API - Slashdot Mozilla Outlines Plan For Manifest V3 Extensions API - Slashdot Mozilla Outlines Plan For Manifest V3 Extensions API - Slashdot

Mozilla Outlines Plan For Manifest V3 Extensions API (mozilla.org) 4

Posted by msmash from the up-next dept.
New submitter q4Fry writes: When Google released its changes to the Chrome WebExtensions API for comment, many groups criticized them for cutting off ad-blockers at the knees. Now, Mozilla has released its plan for following (and departing from) the APIs that Chrome may adopt.

Will Mozilla follow Google with these changes? In the absence of a true standard for browser extensions, maintaining compatibility with Chrome is important for Firefox developers and users. Firefox is not, however, obligated to implement every part of v3, and our WebExtensions API already departs in several areas under v2 where we think it makes sense.

Mozilla Outlines Plan For Manifest V3 Extensions API

Comments Filter:

  • In the absence of a true standard for browser extensions, maintaining compatibility with Chrome is important for Firefox developers and users.

    Fuck Chrome and everything about it.

  • by markdavis ( 642305 ) writes: on Wednesday September 04, 2019 @05:44PM (#59159048)

    I, for one, encourage Firefox from further departing from this so-called “standard” that Google apparently controls. There is no need for it. Yes, it might make it so a single addon doesn’t work directly on both browsers, but why should it? Didn’t before. It will be largely easy to port since it is based on the same structure; that is the important part. Trying to be completely “compatible” will chain and restrict Mozilla to Google’s will and restrictions. We are already clamoring for MORE API capabilities, not fewer. Note that Apple doesn’t use it AT ALL, and has no signs they will. So the only browsers using “Webextensions” are Chrom* and Firefox Quantum.

    • >”I, for one, encourage Firefox from further departing from this so-called “standard”

      Talk about a major typo that changes meaning! That is meant to say “I, for one, encourage Firefox to further depart.” My meaning was probably evident from context.

      That’s what I get for not properly proof-reading.

There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.

Slashdot Top Deals

There are bugs and then there are bugs. And then there are bugs. — Karl Lehenbauer

Close

Close

Slashdot

Working...


Notice: Undefined variable: canUpdate in /var/www/html/wordpress/wp-content/plugins/wp-autopost-pro/wp-autopost-function.php on line 51