Closed Bug 1073 Opened 26 years ago Closed 26 years ago

navigator.preference() not wired up yet

Categories

(Core :: DOM: Core & HTML, defect, P2)

x86
Windows NT
defect

Tracking

()

VERIFIED DUPLICATE of bug 7259

People

(Reporter: angus, Assigned: joki)

Details

I know we brought over libpref, but it doesn't appear to be exposed to JavaScript. navigator.preference(foo) should return value of pref foo navigator.preference(foo,bar) should set pref foo to value bar Obviously when we get security, we'll need to control access to these methods, as we do in Navigator. These methods are useful to me in building an XPFE prefs interface.
Status: NEW → ASSIGNED
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
QA Contact: 4015 → 4616
QA contact re-assigned according to the product areas we're currently working on.
Component: DOM Level 1 → DOM Level 0
Component updated to DOM Level 0.
Target Milestone: M4 → M5
This is not getting done by M4. Moving to M5.
Target Milestone: M5 → M6
Moving out to M7
Target Milestone: M7 → M8
Moving to M8 as I need security before I tie this in.
Target Milestone: M8 → M9
Security not turned on yet. M9
I notice that this is assigned to DOM so I assume this has a required interface, but just in case I'll remark about bug #7380 anyway, that might have some bearing on this.
Target Milestone: M9 → M11
Moving out to M11
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 7259 ***
Status: RESOLVED → VERIFIED
Dupl. Marking verified.
You need to log in before you can comment on or make changes to this bug.