[Webkit-unassigned] [Bug 183648] [iOS WK2] Hit-testing fails when specifying a large top content inset

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Mar 14 18:09:48 PDT 2018


--- Comment #1 from Wenson Hsieh <wenson_hsieh at apple.com> ---
WKWebView conflates obscured insets (which cover parts of the viewport) with content insets (which allow scrolling beyond content bounds in a scroll view).

This manifests in incorrect behavior when computing the unobscured content rect if the web view's scrollview has a top content inset, since we'll think that there's a region as tall as the content inset that obscures the viewport, when in fact, the viewport isn't obscured.

This causes all hit-testing in this region to fail because FrameView::visibleContentRect is wrong.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180315/46bf325c/attachment-0001.html>

More information about the webkit-unassigned mailing list