Bug 183035

Summary: [GTK] imported/w3c/web-platform-tests/html/browsers/the-window-object/apis-for-creating-and-navigating-browsing-contexts-by-name/open-features-negative-innerwidth-innerheight.html is flaky
Product: WebKit Reporter: Miguel Gomez <magomez>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: bugs-noreply, dpino
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Miguel Gomez
Reported 2018-02-22 06:45:56 PST
imported/w3c/web-platform-tests/html/browsers/the-window-object/apis-for-creating-and-navigating-browsing-contexts-by-name/open-features-negative-innerwidth-innerheight.html [ Failure Pass ] Most of the times it passes, but sometimes it fails. Last time it was r228915 which had this diff then failed: --- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/html/browsers/the-window-object/apis-for-creating-and-navigating-browsing-contexts-by-name/open-features-negative-innerwidth-innerheight-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/html/browsers/the-window-object/apis-for-creating-and-navigating-browsing-contexts-by-name/open-features-negative-innerwidth-innerheight-actual.txt @@ -4,5 +4,5 @@ PASS features "innerwidth=-404e1" should NOT set "width=404" PASS features "innerheight=-404" should NOT set "height=404" PASS features "innerheight=-404.5" should NOT set "height=404" -PASS features "innerheight=-404e1" should NOT set "height=404" +FAIL features "innerheight=-404e1" should NOT set "height=404" assert_equals: "innerheight=-404e1 is negative and should result in a minimal-height window" expected 100 but got 600
Attachments
Diego Pino
Comment 1 2020-06-19 00:34:27 PDT
The test(s) filed under this bug have been consistently passing for the last 4000 revisions. Marking bug as fixed. Committed r263254: <https://trac.webkit.org/changeset/263254>
Note You need to log in before you can comment on or make changes to this bug.