Bug 178739

Summary: [iOS] css3/viewport-percentage-lengths/viewport-percentage-lengths-* LayoutTests timing out (window.resizeTo())
Product: WebKit Reporter: Ryan Haddad <ryanhaddad>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: cdumez, simon.fraser, thorton
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=178588
https://bugs.webkit.org/show_bug.cgi?id=179636

Ryan Haddad
Reported 2017-10-24 11:16:57 PDT
The following LayoutTests time out when run on iOS: css3/viewport-percentage-lengths/viewport-percentage-lengths-anonymous-block.html css3/viewport-percentage-lengths/viewport-percentage-lengths-percent-size-child.html css3/viewport-percentage-lengths/viewport-percentage-lengths-relative-font-size.html css3/viewport-percentage-lengths/viewport-percentage-lengths-resize.html --- /Volumes/Data/OpenSource/WebKitBuild/Release-iphonesimulator/layout-test-results/css3/viewport-percentage-lengths/viewport-percentage-lengths-anonymous-block-expected.txt +++ /Volumes/Data/OpenSource/WebKitBuild/Release-iphonesimulator/layout-test-results/css3/viewport-percentage-lengths/viewport-percentage-lengths-anonymous-block-actual.txt @@ -1,46 +1,5 @@ -Test viewport unit sizes work when an anonymous block is involved. +#PID UNRESPONSIVE - com.apple.WebKit.WebContent.Development (pid 26856) +FAIL: Timed out waiting for notifyDone to be called
Attachments
Simon Fraser (smfr)
Comment 1 2017-10-24 13:02:00 PDT
These tests seem to be using window.resizeTo(). Not sure what that does on iOS, but it shouldn't hang the process.
Simon Fraser (smfr)
Comment 2 2017-10-26 10:39:12 PDT
I think "+#PID UNRESPONSIVE" is a lie. This happens for any test that just times out because notifyDone wasn't called. We need to fix that.
Ryan Haddad
Comment 3 2017-10-27 16:08:17 PDT
fast/css-grid-layout/flex-content-sized-columns-resize.html also uses window.resizeTo(). Though, it fails instead of timing out on iOS.
Note You need to log in before you can comment on or make changes to this bug.