1005434 - Leave my customizations alone!

Status: VERIFIED INVALID

(Firefox :: Untriaged, defect)

Description

[Peter Rowell]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140421221237

Steps to reproduce:

I did nothing! FF was auto-upgraded and again(!) for the 6th or 7th time my customizations have been trashed.


Actual results:

The locations of Home and Reload, Tabs on top instead of bottom, the stupid bookmark star, etc., all reverted to *someone else's* idea of where they should be. You're not making things better, you're acting more and more like M$ does when they release garbage like Win 8.


Expected results:

Nothing should have happened! If you're going to spruce up the renedering engine, great! But stop changing my customizations. Stop it! Stop F*cking with where I want things! I swear to God that Chrome is looking better and better the more your UX "experts" keep resetting where things land. There is no excuse except outright laziness to trash explicitly set user preferences.

Just leave the damn things where I (repeatedly) put them!

Comment 1

[Peter Rowell]

Now it turns out I can't even move the damn Reload back to where *I* want it to be. And setting tabsOnTop to true/false makes no difference -- they stubbornly remain on top. Did anyone bother to QA or regression test this release? It's time to either revert to an earlier release of FF or find a browser that respects *user preferences*.

Comment 2

[:Gijs (he/him)]

(In reply to Peter Rowell from comment #1)
> Did anyone bother to QA or regression test this release?

Yup! We thought it was amazing.

Seriously though, I'm sorry our update gave you a bad time. For reference, you can use add-ons like https://addons.mozilla.org/firefox/addon/classicthemerestorer/ to restore some of the customizations you used. All of the issues you mentioned have been discussed at length, both on bugzilla and on the Firefox-dev mailing list ( https://wiki.mozilla.org/Firefox/firefox-dev ).

Because:
- you reported multiple things
- some of them weren't identifiable issues ("stupid bookmark star" is an opinion, not a bug)
- the others being identified and discussed and deliberate;
- of the swearing and other violations of https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

I'm going to close this as invalid. This might be an open bug tracker, but we don't have to put up with being insulted (unless you were trying to compliment us by comparing us with the competition, in which case I'm sorry to say you did not succeed) and yelled at.

If you need help with Firefox, try using https://support.mozilla.org/ .

If you file another bug, please consider reading the previously linked etiquette page carefully, searching for existing bugs covering the issue you've found, and filing one (1) bug per issue, instead of writing up a collection into a single report, because it makes them a lot harder to deal with.

Thank you.

Comment 3

[Peter Rowell]

I did research it and could not find anything that sounded
vaguely like this. This has been an increasingly common problem
with FF releases: new release comes out, some plugins (even
nainstream ones) break, and various UI preferences are set
back to default or (as in this case) made inoperable.

I "fixed" this problem by a) reverting to 28, and b) turning off
auto-updates. I suspect it will be awhile before I have the
time to sample FF 34 (or whatever rev you're at in the future).