3 ms·

Can anyone explain to me the problem? They basically created an OPTION, i.e., optional, that breaks when people who don't get it use it. Now I've got plenty of

Can anyone explain to me the problem? They basically created an OPTION, i.e., optional, that breaks when people who don't get it use it. Now I've got plenty of tech illiterate friends, and they've asked me many questions over the years, but never did it have anything to do with browser settings not loading pictures or javascript. In fact, it's the one thing people tend not to mess with. They'll do tons of weird software, they'll even do regedits from a misinformed guide, but touching browser settings? I don't know about you, but none of my friends ever did. So what's the problem here? Don't see one. What's the solution if there was a problem? Create a 'dev-mode' button, give the user a warning they shouldn't use it unless they're software developers, and put your tricky settings behind that wall. The solution doesn't seem to me to require people to install add-ons for what is basic functionality to a decent amount of people, especially not in an addon store with lots of third-party crap that might work now, but doesn't work in combo with another add-on, or stops working after the browser updates and the add-on dev moved on to other things.

poolpool 12y ago
This attitude is extraordinarily hostile towards users, and even if it wasn't including checkboxes in preferences (especially when you have things like about:config) that disable the entire functionality of the app for 99% of use cases is ridiculous.
Someone1234 12y ago
> What's the solution if there was a problem? Create a 'dev-mode' button, give the user a warning they shouldn't use it unless they're software developers, and put your tricky settings behind that wall. That's my preferred solution. On both Android (tap the build version 7 times) and Chrome (chrome://flags) it works extremely well, allowing you access to settings you wouldn't dream of giving the general public. They could also move some of this from the general settings panel into the Developer Bar. Chrome allows you to disable JavaScript for your current page from there (although it still has the global setting too). I'm all for Firefox reducing the complexity/gotchas within the general public's settings panel. Just allow advanced users to continue to access them via some means and everyone is happy. It wouldn't be a big deal to e.g. have to type in About:DeveloperSettings.

poolpool 12y ago

This attitude is extraordinarily hostile towards users, and even if it wasn't including checkboxes in preferences (especially when you have things like about:config) that disable the entire functionality of the app for 99% of use cases is ridiculous.

Someone1234 12y ago

> What's the solution if there was a problem? Create a 'dev-mode' button, give the user a warning they shouldn't use it unless they're software developers, and put your tricky settings behind that wall. That's my preferred solution. On both Android (tap the build version 7 times) and Chrome (chrome://flags) it works extremely well, allowing you access to settings you wouldn't dream of giving the general public. They could also move some of this from the general settings panel into the Developer Bar. Chrome allows you to disable JavaScript for your current page from there (although it still has the global setting too). I'm all for Firefox reducing the complexity/gotchas within the general public's settings panel. Just allow advanced users to continue to access them via some means and everyone is happy. It wouldn't be a big deal to e.g. have to type in About:DeveloperSettings.