Babele Dunnit wrote:
In fact, I have also a domWindow event listener, and if I
try this stuff on a simple HTML-only page, I can see the "click" event
being dispatched and received by my event listener handler. So far so
good.
Fact is, for SOME sites, this does not happen, i.e. Facebook. In
FaceBook, no matter where I synthesize these events, my event listener
NEVER receives any "click" event. On other sites, like the Google
homepage, I get those "click" events in my listener for some DOM
nodes, and I don't for others (like the "more" drop-down).
Is your listener bubbling or capturing? If the former, are the sites
stopping propagation of the click event when they handle it?
I mean, everything works, nearly. I can navigate, my menus correctly
open and close, and probably I don't get the events because something
somewhere in the sites frameworks intercepts them.
Yep, that's most likely.
You can try attaching your listener as a capturing listener to test this
hypothesis.
This WILL NOT WORK. When I send synthesized mouse events, the "click"
event is NOT generated, my event listener does not receive any
"click", and the "onclick" handler of the search button is not called.
It might be worth trying to create a minimal (in terms of HTML/JS/CSS)
testcase for this. At that point it usually becomes clear what's going
on.... and if it doesn't, you should file a bug.
-Boris
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
