Bug 143692 – [iOS WK2] Interactive elements of developer.apple.com are broken

• Component: New Bugs
• Status: RESOLVED FIXED

[Simon Fraser (smfr)]

[iOS WK2] Interactive elements of developer.apple.com are broken

[Simon Fraser (smfr)]

Created attachment 250690 [details]
Patch

[David Kilzer (:ddkilzer)]

<rdar://problem/19320087>

[Sam Weinig]

Comment on attachment 250690 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=250690&action=review

> Source/WebCore/ChangeLog:9
> +        WHen a composited RenderLayer had nodes in the scrolling tree by virtue of

WHen -> When

> Source/WebCore/ChangeLog:14
> +        Fix by having RnderLayerCompositor::updateScrollCoordinationForThisFrame()

RnderLayerCompositor -> RenderLayerCompositor

> LayoutTests/platform/ios-simulator-wk2/scrolling/remove-scrolling-role.html:41
> +            window.setTimeout(function() {

Why do we need the 0-delay timer here?

[Simon Fraser (smfr)]

(In reply to comment #3)
> Comment on attachment 250690 [details]
> Patch
> 
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=250690&action=review
> 
> > Source/WebCore/ChangeLog:9
> > +        WHen a composited RenderLayer had nodes in the scrolling tree by virtue of
> 
> WHen -> When
> 
> > Source/WebCore/ChangeLog:14
> > +        Fix by having RnderLayerCompositor::updateScrollCoordinationForThisFrame()
> 
> RnderLayerCompositor -> RenderLayerCompositor

This is what happens when typing over a slow VNC connection.

> > LayoutTests/platform/ios-simulator-wk2/scrolling/remove-scrolling-role.html:41
> > +            window.setTimeout(function() {
> 
> Why do we need the 0-delay timer here?

To get an initial layout with the pre-changed style.

[Simon Fraser (smfr)]

https://trac.webkit.org/r182799