Closed Bug 283716 Opened 20 years ago Closed 20 years ago

advanced javascript options missing in new Options Window

Categories

(Firefox :: Settings UI, defect)

Product:
Firefox
Component:
Settings UI
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: Peter6, Assigned: bugs)

References

Details

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050225 Firefox/1.0+ Options->Content enable javascript has no further options, only "but disable common annoyances"
To clarify... without expanding on this as before, it's not at all obvious what these "common annoyances" are, whether users get UI to change them or not.
Flags: blocking-aviary1.1?
There are still leftovers of the advanced script window in the tree: http://lxr.mozilla.org/seamonkey/source/browser/components/preferences/content.js#124 (showAdvancedScript opens the dialog, but this function is called from nowhere) http://lxr.mozilla.org/seamonkey/source/browser/components/preferences/advancedScript.xul (already converted to the new preferences system, but not shipped in the build) http://lxr.mozilla.org/seamonkey/source/browser/locales/en-US/chrome/browser/preferences/advancedScript.dtd (not shipped either)
Deliberate removal of UI is not an actual regression. I happen to agree with the choice Ben has made here, and if there's a desire to have fine-grained UI to manage these prefs, people can do it via extension. Or just use about:config.
Status: NEW → RESOLVED
Closed: 20 years ago
Flags: blocking-aviary1.1?
Keywords: regression
Resolution: --- → WONTFIX
While I agree the javascript options was bad, "disable common annoyances" is very confusing, /maybe/ it needs a better description
(In reply to comment #3) >I happen to agree with >the choice Ben has made here, and if there's a desire to have fine-grained UI >to manage these prefs, people can do it via extension. I can't agree more. (In reply to comment #4) > While I agree the javascript options was bad, "disable common annoyances" is > very confusing, /maybe/ it needs a better description Ben filed a bug for explanating the new stuff
If you're reffering to the "document new options window" bug, that's not an answer ... Other than the security prefs, I shouldn't need to open the help viewer in order to know "What does it do"?
Would a tooltip , based on the prefs settings be suffucient or should the "title" be changed ?
please put the advanced options back. if its in an advanced section, it wont confuse the average user cause they wont go there. and besides, deciding whether u want right click disabled, or status bar disabled is not that confusing.
Can we do a little blue '?' That when hoverd over explains what exactly or in basic but short and to the point terms what "Common annoyances" means?
it wouldnt be that hard to add it back in. steffen said that the function is there. just add a button that calls it.
An extension has been written that provides a UI for changing the advanced javascript preferences in the new options window: http://forums.mozillazine.org/viewtopic.php?t=225697
*** Bug 283855 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > There are still leftovers of the advanced script window in the tree That is no longer true, as Ben has removed that code in one of his recent checkins. http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&date=explicit&mindate=2005-02-26+16%3A29&maxdate=2005-02-26+16%3A29&cvsroot=%2Fcvsroot
Is there somewhere explained, what that "common" means? IMO, it's totally wrong to remove these detailed options.
honestly, as far as I would agree with putting this advanced functionality into an extension (though I don't like that idea very much), an option named "but disable common annoyances" is hilarious. It's like placing a button "clean" on your desktop and you don't know whether it cleans your whole harddisk, or just your temp files. A tooltip would be helpful at least.
I thought "simplifying" meant de-cluttering the UI. Not taking away fine grained control.
I think this should be reopened, at least for further consideration (and perhaps with a different title). Not only does the checkbox present give no clues as to what it enables/disables, but reducing several preferences to a single option makes no sense. For example, I have no idea of what the checkbox state should be if I change one or two of the affected preferences via about:config. If we're looking to declutter the interface, I'd say remove the option entirely and just leave the desired defaults alone, then place the whole "javascript options" in the Advanced part of the options UI. Afterall, if a user doesn't understand "hide the statusbar", then what hope is there for "Use TLS 1.0"?
wouldnt a doable option be to keep the "but disable common annoyances" box, and to also have an "advanced" button? that way, when you click "disable common annoyances", you can go into advanced and see exactly what changes it made. Even further, why not have an about:config entry that enables/disables the VIEWING of the "advanced" button, similar to the <b>browser.tabs.showSingleWindowModePrefs</b> option... I mean, what possible reason could there be to NOT do that
Agreeing with #15 - #18, and suggest a new bug for the problem in #15.
*** Bug 296268 has been marked as a duplicate of this bug. ***
*** Bug 298746 has been marked as a duplicate of this bug. ***
*** Bug 299424 has been marked as a duplicate of this bug. ***
(In reply to comment #15) ... > disable common annoyances" is hilarious. > It's like placing a button "clean" on your desktop and you don't know whether it > cleans your whole harddisk, or just your temp files. That would be the installer. See Bug 302114 installer deletes full directory > A tooltip would be helpful at least. Very! (In reply to comment #18) > wouldnt a doable option be to keep the "but disable common annoyances" box, and > to also have an "advanced" button? that way, when you click "disable common > annoyances", you can go into advanced and see exactly what changes it made. That, or one of those + signs in a box. Then open the + (turns to a -) to see the details and uncheck individual ones if you desire. That is how most other software works nowadays.
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in before you can comment on or make changes to this bug.