Michael Reeves would like Tommy Steimel and Peter Beverloo to review this change.
Document PiP: Align requestWindow timing with the spec
Chromium resolves requestWindow() from the task that dispatches the enter event, so the event fires before promise reactions. The specification instead queues the enter event on the DOM manipulation task source and returns a resolved promise. This causes the requestWindow timing subtest in returns-window-with-document.https.html to fail.
Resolve the promise when the window is created and queue only the enter event. Also make Content Shell close an existing Document PiP window before replacing its child contents, matching Chrome’s PictureInPictureWindowManager and supporting the WPT’s sequential window requests.
Remove the test’s expected-failure baseline now that Chromium follows the specified ordering.
R=pe...@chromium.org, ste...@chromium.org
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |