Stories
Slash Boxes
Comments

SoylentNews is people

posted by CoolHand on Saturday August 22 2015, @05:47AM   Printer-friendly
from the who-is-this-company-named-mozilla dept.

To the surprise of absolutely nobody who's been paying attention the past few years, Mozilla has announced that it will be deprecating all current extensions and have all future extensions be compatible with Chrome and Opera via the new WebExtensions API.

  • We are implementing a new extension API, called WebExtensions—largely compatible with the model used by Chrome and Opera—to make it easier to develop extensions across multiple browsers.
  • A safer, faster, multi-process version of Firefox is coming soon with Electrolysis; we need developers to ensure their Firefox add-ons will be compatible with it.
  • To ensure third-party extensions provide customization without sacrificing security, performance or exposing users to malware, we will require all extensions to be validated and signed by Mozilla starting in Firefox 41, which will be released on September 22nd 2015.
  • We have decided on an approximate timeline for the deprecation of XPCOM- and XUL-based add-ons.

Maybe now we can get a sustainable fork going?


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 5, Informative) by sudo rm -rf on Saturday August 22 2015, @07:26AM

    by sudo rm -rf (2357) on Saturday August 22 2015, @07:26AM (#226180) Journal

    Thanks for the explanation, the Firefox (40) setting is called 'network.dns.disablePrefetch'
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Controlling_DNS_prefetching [mozilla.org]

    Starting Score:    1  point
    Moderation   +4  
       Informative=4, Total=4
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   5  
  • (Score: 2) by Zz9zZ on Saturday August 22 2015, @07:51AM

    by Zz9zZ (1348) on Saturday August 22 2015, @07:51AM (#226184)

    I'm glad it can be disabled, but they've removed the ability to change settings before. Also, nothing should EVER be only accessible through something like about:config. Regular users will never decipher that, or know the option even exists unless told by someone. All browser options should be in the UI with full descriptions so that any human can easily find the preferences/options menu and navigate through all possibilities.

    --
    ~Tilting at windmills~
    • (Score: 2, Interesting) by Anonymous Coward on Saturday August 22 2015, @11:05AM

      by Anonymous Coward on Saturday August 22 2015, @11:05AM (#226220)

      Make sure that flipping that actually disables it. Some of those booleans don't actually do anything because the code ignores their value.