Bug 184210 – REGRESSION (r229828): web view doesn’t update or respond to resizing until client calls policy decision handler

• Status: RESOLVED
• Resolution: FIXED
• Component: WebKit2

In TOT (r230129), WKWebView isn’t updating and responding to resizing between when it calls -webView:decidePolicyForNavigationAction:decisionHandler: and when the client calls the decision handler. To see the bug, build and run attachment 336921 [details]. Click the WebKit link in the window and observe that as long as the sheet is up, the link remains red, the seconds counter isn’t updating, and resizing the window doesn’t cause the yellow rectangle to resize to fit the new width.

Compare to the correct behavior with built-in WebKit in macOS 10.13.4, where the link reverts to inactive color, the numbers keep updating, and the rectangle follows along as the window is resized.

[Radar WebKit Bug Importer]

<rdar://problem/39072354>

[Chris Dumez]

Yes, I caused this by freezing the layer tree during the navigation policy decision.
This change was made to make the async code path more like the old sync code path. Several API tests started failing on iOS when we moved everybody over to the async policy code path. The reason for those failures is that the view would now do an initial layer tree commit for about:blank even though it was navigated to a test page as soon as it was created. This confused the tests which were getting temporarily a blank view and doing things like snapshots.

If it is not acceptable freeze the layer tree during this policy decision then we’ll need to find another solution to make those API tests happy. I thought it was would acceptable because the policy decision is normally quick as most clients respond right away.

[Chris Dumez]

Caused by fix for https://bugs.webkit.org/show_bug.cgi?id=183787

[Chris Dumez]

API tests that were failing on iOS without r229828:
>   DataInteractionTests.AdditionalLinkAndImageIntoContentEditable
>   DataInteractionTests.CanStartDragOnDivWithDraggableAttribute
>   DataInteractionTests.DoNotCrashWhenSelectionMovesOffscreenAfterDragStart
>   DataInteractionTests.DragEventClientCoordinatesBasic
>   DataInteractionTests.DragImageFromContentEditable
>   DataInteractionTests.DragLiftPreviewDataTransferSetDragImage
>   DataInteractionTests.ImageDoesNotUseElementSizeAsEstimatedSize
>   DataInteractionTests.ImageToContentEditable
>   DataInteractionTests.ImageToTextarea
>   DataInteractionTests.InjectedBundleAttachmentElementData
>   DataInteractionTests.InjectedBundleImageElementData
>   DataInteractionTests.LargeImageToTargetDiv
>   ScrollViewInsetTests.RestoreInitialContentOffsetAfterCrash
>   WKWebView.SnapshotImageLargeAsyncDecoding

So we need to find an alternative to r229828 and make sure those API tests still pass on iOS.

[Chris Dumez]

Created attachment 338460 [details]
Patch

[Chris Dumez]

Created attachment 338495 [details]
Patch

[Chris Dumez]

Created attachment 338497 [details]
Patch

[Wenson Hsieh]

Comment on attachment 338497 [details]
Patch

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

> Source/WebCore/ChangeLog:13
> +        To address the issue, this patch revers r229828 and instead updates the iOS

Nit - s/revers/reverts

> Source/WebKit/ChangeLog:13
> +        To address the issue, this patch revers r229828 and instead updates the iOS

Nit - s/revers/reverts

[Chris Dumez]

Committed r230876: <https://trac.webkit.org/changeset/230876>