Open Bug 1549355 Opened 5 years ago Updated 2 years ago

Consider having the widget dispatch synthetic mouse moves


(Core :: Web Painting, enhancement, P3)





(Reporter: kats, Unassigned)


(Blocks 1 open bug)


+++ This bug was initially created as a clone of Bug #1524232 +++

There's some discussion in bug 1524232 comment 9 onwards. Currently we dispatch synthetic mouse events in some scenarios directly to the presShell of the content process that is generating them. However it might make more sense to ask the widget to generate these mouse events so that it ends up targeted to the correct global process in a fission-enabled browser. It's not clear to me exactly what the desired behaviour is and if this would be better. At the very least it would fix bug 1548560.

I seem to remember that dispatching directly to the presshell was important for some reason. Otherwise all that find view code is useless and we can just dispatch top level and let the normal event handling target it. Perhaps layout/style/test/chrome/test_hover.html relies on that?

Not sure what I was remembering exactly, did a try push that should always dispatch to the rootview and it looks green

Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.