90708 2012-07-06 16:10:57 -0700 fullscreen/exit-full-screen-iframe.html is failing 2014-12-18 10:51:53 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Mac All RESOLVED DUPLICATE 139779 https://bugs.webkit.org/show_bug.cgi?id=139778 LayoutTestFailure P2 Normal --- 1 fpizlo webkit-unassigned eric.carlson fpizlo jer.noble mfeil tonikitoo oldest_to_newest 664286 0 fpizlo 2012-07-06 16:10:57 -0700 This test is failing: --- /Volumes/Data/pizlo/secondary/OpenSource/WebKitBuild/Debug/layout-test-results/fullscreen/exit-full-screen-iframe-expected.txt +++ /Volumes/Data/pizlo/secondary/OpenSource/WebKitBuild/Debug/layout-test-results/fullscreen/exit-full-screen-iframe-actual.txt @@ -5,6 +5,6 @@ EVENT(webkitfullscreenchange) TEST(document.getElementById('frame').contentDocument.webkitIsFullScreen==true) OK EVENT(webkitfullscreenchange) -TEST(document.getElementById('frame').contentDocument.webkitIsFullScreen==false) OK +TEST(document.getElementById('frame').contentDocument.webkitIsFullScreen==false) FAIL END OF TEST 664287 1 fpizlo 2012-07-06 16:15:14 -0700 Skipped in http://trac.webkit.org/changeset/122040 664367 2 ap 2012-07-07 01:27:16 -0700 Also fails on chromium: bug 90704. Should r122035 be just rolled out? Filip, please be sure to CC responsible parties when skipping tests. 664410 3 mfeil 2012-07-07 13:38:44 -0700 (In reply to comment #2) > Also fails on chromium: bug 90704. Should r122035 be just rolled out? I believe this test should pass, and that the failure indicates a real problem that needs to be investigated. After webkitCancelFullScreen() is called from JavaScript and the resulting webkitfullscreenchange event is received, webkitIsFullScreen should no longer be true. Rolling out r122035 would revert the failing test, but it would also revert a valid BlackBerry code fix. 664414 4 mfeil 2012-07-07 14:15:29 -0700 (In reply to comment #2) > Also fails on chromium: bug 90704. Note that this test causes EFL and GTK ports to crash, which is are real failures that need to be fixed. See also bug 89817 for my attempt at a patch which would have prevent these crashes but did not pass review. 664447 5 mfeil 2012-07-07 20:22:18 -0700 (In reply to comment #4) > Note that this test causes EFL and GTK ports to crash GTK port crash is now fixed (bug 90719) and this test passes on GTK (see http://build.webkit.org/results/GTK%20Linux%2064-bit%20Release/ ). 664602 6 tonikitoo 2012-07-08 21:04:47 -0700 (In reply to comment #5) > (In reply to comment #4) > > Note that this test causes EFL and GTK ports to crash > > GTK port crash is now fixed (bug 90719) and this test passes on GTK (see http://build.webkit.org/results/GTK%20Linux%2064-bit%20Release/ ). EFL is also fixed in trunk. 915525 7 eric.carlson 2013-08-08 11:35:55 -0700 (In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > Note that this test causes EFL and GTK ports to crash > > > > GTK port crash is now fixed (bug 90719) and this test passes on GTK (see http://build.webkit.org/results/GTK%20Linux%2064-bit%20Release/ ). > > EFL is also fixed in trunk. This test passes on the Mac port as well: http://build.webkit.org/results/Apple%20MountainLion%20Debug%20WK2%20(Tests)/r153825%20(11521)/results.html Un-skipped in https://trac.webkit.org/r153834 . Marking bug as RESOLVED/WORKSFORME. 915588 8 eric.carlson 2013-08-08 14:16:29 -0700 (In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > (In reply to comment #4) > > > > Note that this test causes EFL and GTK ports to crash > > > > > > GTK port crash is now fixed (bug 90719) and this test passes on GTK (see http://build.webkit.org/results/GTK%20Linux%2064-bit%20Release/ ). > > > > EFL is also fixed in trunk. > > This test passes on the Mac port as well: http://build.webkit.org/results/Apple%20MountainLion%20Debug%20WK2%20(Tests)/r153825%20(11521)/results.html > > Un-skipped in https://trac.webkit.org/r153834 . > > Marking bug as RESOLVED/WORKSFORME. Actually the test is flakey on both Mac and EFL ports. Marked as flakey on Mac in https://trac.webkit.org/r153846. 1056822 9 ap 2014-12-18 10:51:53 -0800 *** This bug has been marked as a duplicate of bug 139779 ***