Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!
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.
The trouble with doing something right the first time is that nobody
appreciates how difficult it was.