Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Tuesday August 25 2020, @11:43PM   Printer-friendly
from the no-way-back dept.

Mozilla seems to be hell-bent on alienating users, as they did it again:

An update to the Android flavor of Firefox left fuming punters thinking a bad experimental build had been pushed to their smartphones. In fact, this was a deliberate software release.

A Reg reader yesterday alerted us to an August 20 version bump that was causing so many problems, our tipster thought it was a beta that had gone seriously awry. "To sum it up, on 20th of August, Firefox 79 was unexpectedly forced on a large batch of Firefox 68 Android users without any warning, way to opt out or roll back," our reader reported. "A lot got broken in the process: the user interface, tabs, navigation, add-ons."

Meanwhile, the Google Play store page for the completely free and open-source Firefox has a rash of one-star reviews echoing similar complaints: after the upgrade, little seemed to work as expected.

Among the complaints are a missing back button, frequent browser crashes, and extensions not working.

Sounds like a buggy release for sure. But:

Unfortunately for our source, and the other Firefox for Android users, this isn't a mistaken release or a broken beta build: it's the new version of Firefox for Android, and it's set to hit the UK today, August 25, and the US on the 27th.


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: 3, Informative) by maxwell demon on Wednesday August 26 2020, @08:42AM

    by maxwell demon (1608) on Wednesday August 26 2020, @08:42AM (#1042034) Journal

    That didn't allow sites to override user prefs with stupid "!important" rules

    Educated users use !important themselves on their user prefs. That way the user preferences overrule the site CSS even when the site CSS has !important.

    No need to fix the specification or have browsers not follow it in this case. If your browser doesn't follow it and gives site !important preference over user !important, it is broken and should be fixed.

    --
    The Tao of math: The numbers you can count are not the real numbers.
    Starting Score:    1  point
    Moderation   +1  
       Informative=1, Total=1
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3