Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Sunday August 13 2017, @12:08PM   Printer-friendly
from the firefox-loses-yet-more-users dept.

Firefox 57, which is slated for release on November 14, will "only run WebExtensions", according to Mozilla.

This is expected to break compatibility with many existing Firefox extensions, and in many cases there aren't WebExtensions-compatible alternatives available for these extensions.

During some recent discussion at Slashdot, it became clear that some users have nearly all of their extensions classified as "legacy", and susceptible to breakage.

Members of the SoylentNews community, if you use Firefox, how many of your extensions are set to no longer work with Firefox in the near future?

If Firefox 57 breaks compatibility with your existing extensions, will this finally be enough for you to discard Firefox and find an alternative browser to use?

Will this extension breakage, and subsequent loss of users, effectively end the viability of Firefox as a modern web browser?


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: 2) by arcz on Sunday August 13 2017, @06:04PM (2 children)

    by arcz (4501) on Sunday August 13 2017, @06:04PM (#553318) Journal

    Firefox is a shitty browser. The only reason I use it over chrome is the extensions and the slightly cleaner look with my theme. If the main reason I use firefox, the extensions, no longer works, I will look for a firefox fork. If I don't find one, I'll just use chrome.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Sunday August 13 2017, @07:32PM (1 child)

    by Anonymous Coward on Sunday August 13 2017, @07:32PM (#553339)

    Firefox has been removing controls from users for years now, whereas the mere existence of media.autoplay.allowscripted in Pale Moon (to go alongside Mozilla's media.autoplay.enabled which does NOT prevent a web page from "clicking its own play button") shows that there's a technically sane head behind the upstart's show.

    • (Score: 0) by Anonymous Coward on Monday August 14 2017, @02:56AM

      by Anonymous Coward on Monday August 14 2017, @02:56AM (#553436)

      They were involved in the MU* scene like 20-30 years ago.

      MU*ing has gotten very similiar to Mozilla, insofar that build time options have been removed and many previously configurable features are no longer configurable to administrators or end users in the same ways. New features are great, but breaking your old ones to do so should really be done as a fork, not a 'natural evolution' of the product.