Closed
Bug 800240
Opened 12 years ago
Closed 12 years ago
Unable to create DOM events in extension code injected with Page-Mod
Categories
(Add-on SDK Graveyard :: General, defect, P1)
Tracking
(firefox16+, firefox17-)
RESOLVED
WONTFIX
People
(Reporter: urban_duckman, Assigned: irakli)
Details
Attachments
(1 file)
165 bytes,
text/html
|
Details |
Hello. I am an engineer at Yahoo! and I work on Yahoo! Axis. Yahoo! Axis facilities some layers of communication between the extension client (created using Jetpack) and the code we inject in page (and it's child <iframe>s) by using custom events, created using simple DOM event calls like: var evt= document.createEvent("Event"); evt.initEvent("NanoBridgeEvt", true, true); elem.dispatchEvent(evt); etc. On FF16 Beta, this code does not work anymore. The call to initEvent throws an exception, and the exception is malformed (the object is empty). We found that initEvent calls do not throw from <iframes> created within the injection region. It only throws from the same level as the document itself. Even in this case, the recipient of the call sees a malformed event object. I was able to work around this by using a CustomEvent() object as documented at https://developer.mozilla.org/en-US/docs/DOM/Event/CustomEvent?redirectlocale=en-US&redirectslug=DOM%2FcustomEvent. However, even then the recipient of the event gets a malformed event object (object is empty, no members). This is a high priority issue for Yahoo! as this bug breaks our Yahoo! Axis extension which we are heavily promoting. We have a workaround for the issue but we would prefer to see Mozilla fix what we believe to be a bug in FF16 beta before you guys push it live for autoupdates.
Comment 1•12 years ago
|
||
cc'ing mossop and gavin: Do do guys know someone who could help here? Thanks!
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•12 years ago
|
tracking-firefox16:
--- → ?
Keywords: regression,
regressionwindow-wanted
Updated•12 years ago
|
Component: Extension Compatibility → General
Product: Firefox → Add-on SDK
Version: 16 Branch → unspecified
Comment 2•12 years ago
|
||
Here is a testcase that can help diging into this. I wasn't able to see it failing on Nightly nor current Firefox beta.
Attachment #670436 -
Flags: review?(rFobic)
Comment 3•12 years ago
|
||
(In reply to Alexandre Poirot (:ochameau) from comment #2) > Created attachment 670436 [details] > Pull request 603 > > Here is a testcase that can help diging into this. > I wasn't able to see it failing on Nightly nor current Firefox beta. Is this a content-proxy issue? Those are enabled in Fx 16 and disabled in Fx 17 (beta)
Priority: -- → P1
Comment 4•12 years ago
|
||
(In reply to Paul Broman from comment #0) ... > This is a high priority issue for Yahoo! as this bug breaks our Yahoo! Axis > extension which we are heavily promoting. We have a workaround for the > issue but we would prefer to see Mozilla fix what we believe to be a bug in > FF16 beta before you guys push it live for autoupdates. Hi Paul, I agree this is a high priority issue, however we are having some issues reproducing the problem. What would help us most is if you could provide a reduced test case that exhibits the problem? If you need to, feel free to contact me directly.
Updated•12 years ago
|
Flags: needinfo?(urban_duckman)
Comment 6•12 years ago
|
||
Is there some reason you can't add the relevant info to the bug? Re-adding needinfo flag until we have a public testcase.
Flags: needinfo?(urban_duckman)
Comment 7•12 years ago
|
||
I've got the info and am looking into it, will report back as events warrant.
Flags: needinfo?(urban_duckman)
Comment 8•12 years ago
|
||
We need to know if this is a regression that only affects the SDK, or if it is a regression in Firefox that could have an impact on other add-ons.
Updated•12 years ago
|
tracking-firefox17:
--- → ?
Comment 10•12 years ago
|
||
After some investigation by Kris, it looks like this is an issue related to using an older version of the SDK, although I would like to get confirmation from Paul or someone from his team before we close this bug.
Flags: needinfo?(urban_duckman)
Comment 11•12 years ago
|
||
Will not track for 17 in that case, please renominate if comment 10 is incorrect.
Comment 12•12 years ago
|
||
Since this appears to be an old SDK problem and the developer has worked around it anyway, I don't think there's any reason to keep this open. Please reopen if the problem turns out to be anything else.
Status: NEW → RESOLVED
Closed: 12 years ago
Keywords: regression,
regressionwindow-wanted
Resolution: --- → WONTFIX
Reporter | ||
Comment 13•12 years ago
|
||
Just FYI, this bug did not repro once I repacked our extension with Jetpack 1.10.
Flags: needinfo?(urban_duckman)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → rFobic
Comment 14•11 years ago
|
||
Comment on attachment 670436 [details]
Pull request 603
Another test patch landed.
Attachment #670436 -
Flags: review?(rFobic)
You need to log in
before you can comment on or make changes to this bug.
Description
•