NEW290666
REGRESSION(iOS 18): [ iOS ] imported/w3c/web-platform-tests/screen-orientation/fullscreen-interactions.html is a flaky failure.
https://bugs.webkit.org/show_bug.cgi?id=290666
Summary REGRESSION(iOS 18): [ iOS ] imported/w3c/web-platform-tests/screen-orientatio...
Yasmin Karimi
Reported 2025-03-28 17:43:42 PDT
imported/w3c/web-platform-tests/screen-orientation/fullscreen-interactions.html This test is a flaky failure on iOS. HISTORY: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fscreen-orientation%2Ffullscreen-interactions.html TEXT DIFF: @@ -1,4 +1,4 @@ -PASS fullscreen and orientation support -PASS Iframe can't itself know if it's parent is fullscreen when changing orientation +FAIL fullscreen and orientation support promise_test: Unhandled rejection with value: object "TypeError: Cannot request fullscreen without transient activation." +FAIL Iframe can't itself know if it's parent is fullscreen when changing orientation promise_test: Unhandled rejection with value: object "TypeError: Cannot request fullscreen without transient activation." DIFF URL: https://build.webkit.org/results/Apple-iOS-18-Simulator-Release-WK2-Tests/292784@main%20(1190)/imported/w3c/web-platform-tests/screen-orientation/fullscreen-interactions-pretty-diff.html REPRODUCIBILITY: I was unable to reproduce on the iOS 18.2 simulator. REGRESSION: This test began timing out more consistently when moved from iOS 17 to iOS 18, however it was still flakily failing before this point. This shows the regression more clearly: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fscreen-orientation%2Ffullscreen-interactions.html&recent=false&version_name=iOS%2018&version_name=iOS%2017
Attachments
Radar WebKit Bug Importer
Comment 1 2025-03-28 17:43:50 PDT
EWS
Comment 2 2025-03-28 18:02:51 PDT
Test gardening commit 292864@main (a84421bce22a): <https://commits.webkit.org/292864@main> Reviewed commits have been landed. Closing PR #43225 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.