Bug 183144 – [WPE] testRunner.setWindowIsKey() has no effect on the web process side in WebKit2

• Status: NEW
• Component: Tools / Tests

[Daniel Bates]

The WPE implementation of testRunner.setWindowIsKey() only updates a boolean flag and does not change the activation state of the window. We need to fix it up so that it actually changes the activation state of the window so as to be able to test page activation issues. Once we implement such behavior we may be able to unskip some or all of the following tests:

fast/dom/Window/window-focus-self.html
fast/events/blur-focus-window-should-blur-focus-element.html
fast/selectors/querySelector-window-inactive.html
fast/selectors/selection-window-inactive.html
scrollbars/corner-resizer-window-inactive.html

[Michael Catanzaro]

WPE has no concept of window focus. I'm not sure what the expected behavior for these tests should be; it will require some thinking. Perhaps it should behave as if the window is always focused.

[Daniel Bates]

(In reply to Michael Catanzaro from comment #1)
> WPE has no concept of window focus. I'm not sure what the expected behavior
> for these tests should be; it will require some thinking. Perhaps it should
> behave as if the window is always focused.

The tests do not seem applicable to WPE. We should mark then as WONTFIX in WPE’s TestExpectations. These tests are explicitly testing the behavior of the non-standard ::selection:window-inactive selector to match selected text when the window is deactivated (i.e. not the frontmost focused window). Towards that, testRunner.setWindowIsKey() allows a test to make the window activated (frontmost focused) or deactivated (background; defocused).