Hello Boris, you're right - it's not XUL/HTML difference, but a chrome/content one. The issue with React and privileged iframes was investigated here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1245921#c55 see comments 55 and on. Jarda On Tue, Jan 17, 2017 at 6:05 PM, Boris Zbarsky <bzbar...@mit.edu> wrote: > On 1/16/17 4:31 PM, Jaroslav Šnajdr wrote: > >> - there is a difference in how events are dispatched in HTML vs XUL >> iframes. In HTML, the capture/bubble phases are isolated inside the iframe >> window, but in XUL, the target chain crosses the iframe boundaries. >> > > I'm not aware of this behavior for XUL, nor do I see anything obvious in > the event code that would cause such a thing to happen. Are you sure this > is the behavior you're seeing (as opposed to the "dispatch to the chrome > event target when reaching a window" behavior which we _do_ have and which > is not XUL-specific, but rather chrome-docshell specific)? > > -Boris > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
