Closed
Bug 436800
Opened 16 years ago
Closed 16 years ago
setElementValue method needs to deal with preference on a button
Categories
(Toolkit :: Preferences, defect)
Toolkit
Preferences
Tracking
()
RESOLVED
INVALID
People
(Reporter: iannbugzilla, Assigned: iannbugzilla)
References
()
Details
Attachments
(1 file)
When a boolean preference is assigned to a button then if it is set to true it should disable the button as it did under the way things were done under xpfe preferences. i.e. <button label="&button.label;" preference="pref.browser.disable_button.foobar"/> e.g. http://lxr.mozilla.org/seamonkey/source/browser/components/preferences/privacy.xul#141 http://lxr.mozilla.org/seamonkey/source/browser/components/preferences/privacy.xul#166
This brings back functionality that was present under xpfe preferences and is still trying to be used within Firefox preferences (see above for examples).
Attachment #323306 -
Flags: review?
Attachment #323306 -
Flags: review? → review?(gavin.sharp)
Updated•16 years ago
|
Assignee: nobody → iann_bugzilla
Status: ASSIGNED → NEW
Updated•16 years ago
|
Status: NEW → ASSIGNED
Comment 2•16 years ago
|
||
I had the impression that it was an intentional design decision to only support disable_button when the pref was locked (since it's pretty pointless otherwise). With a locked pref, don't you hit the first two conditions (this.locked and then !this.isElementEditable), and thus correctly set it disabled and return?
Attachment #323306 -
Flags: review?(gavin.sharp)
As per comment 2
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•