Closed
Bug 684448
Opened 13 years ago
Closed 5 years ago
Registering an nsIDOMGlobalPropertyInitializer using "category JavaScript-global-property" has no effect in Fennec
Categories
(Firefox for Android Graveyard :: Extension Compatibility, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jruderman, Unassigned)
Details
Attachments
(2 files)
17.83 KB,
patch
|
Details | Diff | Splinter Review | |
534 bytes,
text/html
|
Details |
I installed https://www.squarefree.com/extensions/domFuzzLite2.xpi in Fennec (after adding a targetApplication) and it didn't work. When I tried to use fuzzPriv in a content process, I just get "fuzzPriv is not defined", with no indication that my component was even loaded. I need this in order to run my DOM fuzzer on Fennec.
Reporter | ||
Comment 1•13 years ago
|
||
Alon Zakai suggest that I try my code as "part of the browser", to find out whether the bug is specific to extensions. It does work when "part of the browser", so I guess the bug is specific extensions. Based on https://bug669240.bugzilla.mozilla.org/attachment.cgi?id=555878
Reporter | ||
Updated•13 years ago
|
Whiteboard: [sg:want]
Reporter | ||
Comment 2•13 years ago
|
||
A simple way to tell whether the fuzzPriv object is working.
Reporter | ||
Updated•13 years ago
|
Blocks: domFuzzFennec
Comment 3•13 years ago
|
||
Jesse, we don't load extension's components in the content process, but you can do it yourself in a frame script, and use the category manager to register the component in the appropriate category.
Reporter | ||
Comment 4•13 years ago
|
||
I'll try that. Seems to defeat the purpose of declarative, low-performance-impact APIs, though :(
Reporter | ||
Comment 5•13 years ago
|
||
How do I tell addCategoryEntry where to find the component?
Comment 6•13 years ago
|
||
Adblockplus is doing it like this: https://hg.adblockplus.org/adblockplus/file/ca58ad5ea9b1/modules/ContentPolicyRemote.jsm
Reporter | ||
Comment 7•13 years ago
|
||
Ian Melven helped port the DOM fuzzer extension to frame scripts and DOMWindowCreated events, so this doesn't block DOM fuzzing of Fennec any more. But it's sad that the nsIDOMGlobalPropertyInitializer API doesn't work in Fennec, since it has such great performance characteristics.
No longer blocks: domFuzzFennec
Whiteboard: [sg:want]
Comment 8•5 years ago
|
||
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•