Closed Bug 873740 Opened 12 years ago Closed 12 years ago

Add an ability to toggle JavaScript easily and conveniently

Categories

(Firefox :: Settings UI, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: r_rom, Unassigned)

References

Details

Because implementation of the bug 851702 has made Firefox less convenient, I request that the ability to toggle JavaScript easily and conveniently be added back. It could be under the Web Developer menu item or anywhere else, but not about:config. The key is easily and conveniently.
Severity: normal → enhancement
Blocks: 851702
Component: General → Preferences
OS: Windows 8 → All
Hardware: x86_64 → All
We just removed it from the main preferences UI with ample reasoning provided by our UX team, so it's unlikely to be making a comeback there. The Web Developer team is talking about making it an option in their UI in bug 864249, so I'm marking this as a duplicate.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
I've read your "ample reasoning" and found them unconvincing. They seemed as solutions waiting for a problem to solve. Bug 864249 is insufficient for what I (actually, many of power users) need. In that bug they want to "only actually disable JS while the toolbox is open". I don't want to have a toolbox open. I want to be able to simply disable JavaScript for a page or globally while seeing the entire page uncluttered by a toolbox. If you, guys responsible for removing the needed features, move it to an extension, I'd OK with that.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
You can use NoScript to disable JavaScript on a per-domain basis.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → WONTFIX
I agree globally with Roman here. This bug is not a duplicate. The toolbox way is not a convenient ability. Even the pref that Firefox 23 has eaten, I find it too difficult. What I would like is a switch in the bottom right of the window, always at hand.
You need to log in before you can comment on or make changes to this bug.