[Webkit-unassigned] [Bug 179735] window.scrollTo is initially unclamped on iOS

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 13 23:07:26 PST 2018


--- Comment #3 from Frédéric Wang (:fredw) <fred.wang at free.fr> ---
(In reply to Ali Juma from comment #0)
> I wonder if a better approach might be to continue sending an unclamped
> scroll offset to the UI process, but in the meanwhile use a clamped scroll
> offset to update FrameView's scroll position. That would mean changing
> AsyncScrollingCoordinator::requestScrollPositionUpdate to take both a
> clamped and an unclamped offset, so that it can use the clamped version for
> the call to updateScrollPositionAfterAsyncScroll (which is what updates
> FrameView's scroll offset).

@Ali: How about just putting back the clamping for programmatic scroll? i.e.

-    ScrollPosition newScrollPosition = !delegatesScrolling() ? adjustScrollPositionWithinRange(scrollPosition) : scrollPosition;
+    ScrollPosition newScrollPosition = (!delegatesScrolling() || inProgrammaticScroll()) ? adjustScrollPositionWithinRange(scrollPosition) : scrollPosition;

What would be the problem if programmatically-set position overrides the one in the UI process?

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/20180214/f0de5130/attachment.html>

More information about the webkit-unassigned mailing list