1036154 - [e10s] Consider adding a generic mechanism to toggle IsHandlingUserInput to the message manager

Status: NEW

(Core :: DOM: Events, defect, P4)

Description

[Blake Kaplan (:mrbkap) (inactive)]

In bug 1001957, billm and I changed a synchronous call between the parent and child to be asynchronous. This caused us to fail an accessibility test because it was expecting the value of EventStateManager::IsHandlingUserInput to be true for the case when the user presses F5 to reload the page. For that bug, I wrote a very narrow patch: in the reload path, we manually set the value of IsHandlingUserInput; however, multiple people have suggested that this should happen automatically.

When I mentioned this to bent, he didn't like this idea and because this is the first time that we've seen a problem like this, there isn't a strong reason to do this work. However, if we do come across another case like this, we probably should consider doing something like encoding IsHandlingUserInput in messages and setting it in the child when we process that message (or something like that).