3 ms·
Yeah instead Addons have to direct the user to manually modify CSS, thus perfectly protecting the sanctity of the browser UI for all time. Mozilla, I'm going t
by FeepingCreature 6y ago
Yeah instead Addons have to direct the user to manually modify CSS, thus perfectly protecting the sanctity of the browser UI for all time.
Mozilla, I'm going to use very small words here so that you understand: users will want to change your UI. You can't fight that without fighting your own users. Then again, that doesn't seem to be stopping them.
- majewsky 6y agoMozilla understands that very well. Otherwise userChrome.css wouldn't exist. They just made it so that it's abundantly clear that if you screw up your userChrome.css, it's your fault, not Mozilla's.
- FeepingCreature 6y agoYeah, which is bullshit. You can't both say "well we let you do it, we're so customizable" and "but if you do and anything goes wrong, it's your fault." I'd rather that userchrome get removed and Firefox own up to the fact that they're not gonna properly support what users want. A company who puts users first should not be ashamed of supporting their users' desires. You either support your users or you fight your users. Mozilla have somehow decided to publicly fight their users and furtively and abortively support them in secret; I really don't get how they think that reflects well on them. It feels like Moz are more trying to appease their own UX designers than their userbase.
- eitland 6y agoA better solution would probably be to add a proper API to move the tabs around and then some possibility to customize them. FWIW Mozilla even experimented with vertical tabs, only they made the tab column so high it interfered with the URL bar and also didn't support nesting.