Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Monday November 28 2016, @07:15PM   Printer-friendly
from the replacing-working-stuff-with-unfinished-technologies dept.

Martin Brinkmann reports via gHacks:

Mozilla announced a couple of days ago that it plans to make Firefox support only WebExtensions add-ons by the end of 2017.

While that seems far far away right now, it is almost certain that things won't be ready by then. What I mean by that is that WebExtensions capabilities won't match those of Firefox's current system. While popular add-ons like NoScript will likely be ported over thanks to Mozilla working with developers actively on implementing missing API features, the same cannot be said for other add-ons.

[...] A recent post by Aris, developer of Classic Theme Restorer (CTR) and several other popular add-ons such as Classic Toolbar Buttons, NewScrollbars, or GlassMyFox, suggests that Classic Theme Restorer may be dead by the end of 2017. While Aris seems to have interest in porting over his extensions to WebExtensions, he notes that this is not possible right now.

Now [it's] real. CTR as we know it (and all my other Firefox add-ons), will be discontinued by the end of 2017. We still have no way to change [the] Firefox UI using WebExtensions and all my add-ons are about UI modifications. Seems like [it's] almost time to get used to another browser.

The end of the popular browser extension would bring the Australis design of Firefox to all users who relied on Classic Theme Restorer up until that point.

This highlights one of the main concerns that the move to WebExtensions exclusivity raises: The APIs are not there yet. In fact, a whole category of add-ons--all that modify the browser UI--cannot be ported over because of missing APIs and the situation may be similar in other areas. What makes this even more problematic than it is is that [...] no one seems to know whether the capabilities that WebExtensions APIs will deliver, once they are made available, will be sufficient to port add-ons over.

[...] Mozilla could have waited with the move until APIs are ready for the most part, but the organization decided not to do so.


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: 0) by Anonymous Coward on Monday November 28 2016, @09:18PM

    by Anonymous Coward on Monday November 28 2016, @09:18PM (#434229)

    Maybe try Vivaldi [vivaldi.com]? Not sure it will fix UI woes, but it certainly fixed my non-configurability woes. Supports Chrome extensions, too.

  • (Score: 1, Insightful) by Anonymous Coward on Monday November 28 2016, @09:22PM

    by Anonymous Coward on Monday November 28 2016, @09:22PM (#434230)

    Closed source browser? You best be joking...

  • (Score: 1, Insightful) by Anonymous Coward on Monday November 28 2016, @11:36PM

    by Anonymous Coward on Monday November 28 2016, @11:36PM (#434280)

    Read their EULA carefully. Pretty sure Vivaldi phones home.

    If you have minimal requirements, you could check out Min [github.io].

    • (Score: 2) by FatPhil on Tuesday November 29 2016, @11:08AM

      by FatPhil (863) <pc-soylentNO@SPAMasdf.fi> on Tuesday November 29 2016, @11:08AM (#434410) Homepage
      Min is based on Electron. Electron is based on Chromium and Node.js. There's little that is minimal about min.
      --
      Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves