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: 4, Informative) by Magic Oddball on Tuesday November 29 2016, @12:48AM

    by Magic Oddball (3847) on Tuesday November 29 2016, @12:48AM (#434294) Journal

    From http://linux.palemoon.org [palemoon.org]

    Installation, uninstallation and upgrades are normally managed with the Pale Moon for Linux installer. However, you can also download Pale Moon for Linux as a bzipped tarball that can be extracted and run from any location on your system.

    You can also install one of these fully-endorsed third-party builds of Pale Moon for Linux:

            Repositories for Debian and Ubuntu -- Maintained by Steve Pusser
            Pale Moon for Linux - SSE-only build -- Maintained by Walter Dnes

    Additionally, Pale Moon is included in and can be installed directly from the default repositories of the following distros:

            Manjaro
            PCLinuxOS
            Puppy Linux
            MEPIS/MX-15
            Arch User Repository (AUR)
            Gentoo Overlays
            Slackbuilds

    Having used all three approaches, I can say they all work just fine.

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

    Total Score:   4