Closed
Bug 439690
Opened 16 years ago
Closed 2 years ago
Code inside two nested objects under hiddenDOMWindow runs unprivileged
Categories
(Core :: DOM: Core & HTML, defect, P5)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INVALID
People
(Reporter: Manuel.Spam, Unassigned)
Details
Attachments
(1 file)
1.25 KB,
application/gzip
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13) Gecko/20080328 SeaMonkey/1.1.9 Build Identifier: If I create one object under hiddenDOMWindow (to have my stuff centralized), then anything works well, but if I create "sub-objects" inside this context, then my "sub-classes" run unprivileged. Maybe someone is able to debug this problem and to find out why privileged code loses its privileged status here. Reproducible: Always
Reporter | ||
Comment 1•16 years ago
|
||
This is a minimal testcase. Just untar into "extensions" directory of SeaMonkey 2.x or Firefox 2.x or 3.x. You should get the appVersion twice, but you'll get it only once. In error console you'll see that the code running into the "second level" of objects lost its privileged status for some reason. I was also able to reproduce this with SeaMonkey 1.x, but there this testcase doesn't work.
Comment 2•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven't been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
Comment 3•2 years ago
|
||
Hi, reporter! I would like to confirm or close this old issue.
Can you explain how the minimal test case should be used?
Can you still reproduce it?
Is it platform-specific (Windows/MacOS/Linux)?
Thanks!
Flags: needinfo?(Manuel.Spam)
Reporter | ||
Comment 4•2 years ago
|
||
Actually this was for an Add-on. I had used "hiddenDOMWindow" to store global data and objects. Because of this bug, I then switched to "jsm" for my global module.
And today this is all obsolete anyway as the only way to develop Add-ons is the new WebExtension API which makes storing global stuff pretty easy without hacking with Firefox internals.
I don't know if this ever was fixed but to be honest I no longer care as the usecase no longer exists. Closing as INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(Manuel.Spam)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•