Bug 1709125 Comment 49 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

How bad an idea would it be to introduce a new vendor-specific event enabled only when tests are running, let's say `MozBrowsingContextFocus` that would first fire right after `focus` on a DOM window that a `focus` event fires on and thereafter would asynchronously fire on each DOM window up the ancestor chain?

This way, the harness could listen for this even on `desiredWindow` without having to figure out which descendant the focus will be restored to.

In addition to Neil already being needinfoed, needinfoing Nika for additional Fission perspective and annevk in case I've missed some existing Web Platform capability.
How bad an idea would it be to introduce a new vendor-specific event enabled only when tests are running, let's say `MozBrowsingContextFocus` that would first fire right after `focus` on a DOM window that a `focus` event fires on and thereafter would asynchronously fire on each DOM window up the ancestor chain?

This way, the harness could listen for this event on `desiredWindow` without having to figure out which descendant the focus will be restored to.

In addition to Neil already being needinfoed, needinfoing Nika for additional Fission perspective and annevk in case I've missed some existing Web Platform capability.

Back to Bug 1709125 Comment 49