Live data from Hacker News

"Disable Javascript" option removed in Firefox 23

bugzilla.mozilla.org

231–240 of 373 posts

Re: "Disable Javascript" option removed in Firefox 23

#231

Earlier quoted context omitted.

Yes, that is correct. It is an EU law. It is an absolutely horrible, ill thought out law, but it is a law, so we all have to comply :-(

Actually, it's possible to implement in it an unobtrusive way that makes users feel more comfortable. The huge popups usually comes from the same websites that do popover ads (that commonly end up invisible and blocking scrolling with adblock) and auto-play videos. Most of the time it's a small bar on the top or bottom of the screen. Stop whining.

Dumb lawers litter my web. Whining is the only thing I can do. Besides, even small bar often becomes huge bar on mobile.

Re: "Disable Javascript" option removed in Firefox 23

#232
post #169

Earlier quoted context omitted.

I have to say that this article is actually quite terrible, as is the opinion that any option that might ever be confusing to a user is an option that shouldn't ship with the product. The thesis of the article is: "Well, we have met the enemy, and he is us.* In the currently shipping version, Firefox ships with many options that will render the browser unusable to most people, right in the main settings ui." The solu…

This was true 10 years ago. These days, every additional setting the application has is a liability. There is a growing group of people, who are scared to have conversation with their browser and make any informed decisions. They ignore such messages. Other people will change any setting they can find and then forget about it. Then they will be surprised and angry at the application that it is not working. My experie…

Removing options is NOT the way to go. If anything, there should be more options, until computers understand natural language.

To be most intuitive to use, computers should converse like a human. Humans have LOTS of options, and everyone understands that. E.g. if I ask a human to make a sandwich, I can specify all the ingredients I want, how and when I want it, and so on.

The ideal computer, too, would adjust its software to my preference. E.g. if I can, using natural language, explain the computer that I want JavaScript disabled, it can figure out what that means and what in the source code or flags of Firefox it has to change for me to have that disabled. Or if I tell it I want a big refresh button in the center of the screen, it can improvise and render one for me.

Far future of course, but that is the most intuitive end goal of computers: you ask them what you want in natural language, they understand and provide it.

For now, because the above does not yet work, please provide options. Fortunately Firefox provides many options for those who need them: about:config. I find it really awesome if you can adjust an application to your needs at such fine grained level.

Re: "Disable Javascript" option removed in Firefox 23

#233
post #52
post #27

I can't remember the last time I wrote an application that didn't rely on Javascript for even parts of its basic functionality. I simply don't understand why you would want to browse the web without JS enabled and the average user definitely would never turn it off except in error, causing them to think the browser is broken. Every single common-use browser on the Internet supports Javascript, there is no reason to a…

> I simply don't understand why you would want to browse the web without JS enabled It's faster. Much faster. Every time I disable noscript to use some website (90% of the time it's video that doesn't work) I'm always astonished how much GARBAGE most website have. Totally useless stuff. Popup boxes, annoying underlining with mouse overs, certificate verifiers, bookmarks, social network promoters, chat boxes, and help…

I use Ghostery to remove analytics and stupid buttons. I sometimes have to disable it for broken websites, but that's relatively rare.

Re: "Disable Javascript" option removed in Firefox 23

#234
post #215

The following rant is somewhat tangential but, as a front-end developer that takes pride in progressively enhancing websites I work on, I think this is a shame for a different reason. So many times when speaking to employers/product owners about progressive enhancement of JavaScript components, the answer I get back is along the lines of "we don't care about that" or "we don't have the time". Sometimes in conversatio…

Shouldn't progressive enhancement be part of best practices, rather than a billable feature on the invoice? Or in other words, used by default.

Re: "Disable Javascript" option removed in Firefox 23

#236
post #220

Earlier quoted context omitted.

When I said "customizable" I didn't mean in terms of settings, but it terms of what you can do with Extensions/Add-ons. Name another browser where the Firebug-like functionality is an extension and not something built-in.

That's a very arbitrary line to draw. Some "alternative browsers" exist that wrap the IE rendering engine in a different UI (and some of those include their own firebug-like functionality), does that mean IE is more customizable than firefox (which, after all, forces you to use GTK for your UI)?

Wrapping the IE rendering engine in a different UI is a different browser, but further than that, you can also embed Gekko, Firefox's rendering engine in a custom UI.

Examples of browsers that embedded Gekko: Camino (a Firefox fork for OS X that happened in a time when Firefox wasn't as polished for OS X), Flock and K-Meleon. Google's Picassa for Linux was also using Gekko.

Also, Firefox's UI toolkit is not GTK, but rather XUL+XPCOM, abstracting over the various native toolkits: https://developer.mozilla.org/en/docs/XUL

Only Firefox on Linux uses GTK. Even on Linux, there have been previous attempts at supporting Qt as the backend for KDE, but all failed because of the easiness with which you can make GTK look like whatever KDE theme you've got selected - not perfect, but the flaws where not enough to gather interest in further development.

There's even XULRunner, for easily building and packaging XUL+XPCOM standalone apps: https://developer.mozilla.org/en-US/docs/XULRunner

This isn't to say that XUL/Gekko are perfect as their complexity was often the subject of criticism, which is why Mozilla replaced XUL completely with HTML5 in Firefox OS and will probably do so in future Firefox versions - as they are also working on Servo, a next-gen rendering engine that doesn't do XUL anymore: http://www.mozilla.org/en-US/research/projects/

Imagine a browser who's every facet and functionality is customizable by HTML5/Javascript extensions that you can install with one click. That's what Firefox already is - the Emacs of browsers.

For example, if my Firebug example wasn't enough, when Chrome was released, many people loved the light download progress functionality that wasn't opening an annoying modal window. Pretty soon an extension called the Download Statusbar happened: https://addons.mozilla.org/en-US/firefox/addon/download-stat...

Re: "Disable Javascript" option removed in Firefox 23

#237
post #220

Earlier quoted context omitted.

When I said "customizable" I didn't mean in terms of settings, but it terms of what you can do with Extensions/Add-ons. Name another browser where the Firebug-like functionality is an extension and not something built-in.

That's a very arbitrary line to draw. Some "alternative browsers" exist that wrap the IE rendering engine in a different UI (and some of those include their own firebug-like functionality), does that mean IE is more customizable than firefox (which, after all, forces you to use GTK for your UI)?

Yes, Firefox is still more embeddable than IE (although that is changing, since almost no one does).

And it doesn't force you to use GTK for your UI.

Re: "Disable Javascript" option removed in Firefox 23

#238
post #195

Earlier quoted context omitted.

Sure, blame the 'checkboxes' and not your own failure to handle disabled js gracefully. I'd be mad about this, except I haven't used firefox in years. One less reason to go back I guess.

Lots of the Web does not do graceful degradation to fully functional sites without JS. That ship has sailed, that battle has been lost. JavaScript is a required, not optional, part of a lot of the Web.

Strongly disagree. Lots of the web may not degrade gracefully, but then also lots of it does.

Further, the notion of it as a lost battle is unfortunate because we're not discussing a binary choice between two opposing sides here. As an approach, progressive enhancement of JavaScript UIs enables developers to deliver an experience that degrades sanely in non-JS environments.

However, I will concede that your opinion appears to be the most commonly-held one, even among some developers. And it's probably not going to change for the better with news like this Firefox development... :-/

Re: "Disable Javascript" option removed in Firefox 23

#239
post #215

The following rant is somewhat tangential but, as a front-end developer that takes pride in progressively enhancing websites I work on, I think this is a shame for a different reason. So many times when speaking to employers/product owners about progressive enhancement of JavaScript components, the answer I get back is along the lines of "we don't care about that" or "we don't have the time". Sometimes in conversatio…

Shouldn't progressive enhancement be part of best practices, rather than a billable feature on the invoice? Or in other words, used by default.

Absolutely! But I still find myself having to make the case for it, when others are looking for ways to cut corners.

Re: "Disable Javascript" option removed in Firefox 23

#240

Earlier quoted context omitted.

Sure, there's a browser for power users. It's called being enough of a power user to install extensions that do what you want.

Actually, it's called coding them myself, but even then I'd rather do that in C than with several layers of abstraction (coding in javascript for a XUL interface or whatever that is -- let me know how startup and runtime performance works out for you when you have 50 of them and 50 tabs open).

Then embed Webkit (or even Xulrunner, but that's painful) and go from there. Good luck.
Post reply on HN