[Webkit-unassigned] [Bug 176243] requestAnimationFrame causes bad location of position:fixed inside overflow:auto and iframe
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Nov 13 10:15:48 PST 2017
https://bugs.webkit.org/show_bug.cgi?id=176243
--- Comment #3 from Frédéric Wang (:fredw) <fred.wang at free.fr> ---
I did a quick debugging of this and the trace for requestAnimationFrame is something like:
RemoteLayerTreeDrawingArea::flushLayers
|
(Timer)
|
RemoteLayerTreeDrawingArea::scheduleCompositingLayerFlush
ScriptedAnimationController::scheduleAnimation
ScriptedAnimationController::registerCallback
Document::requestAnimationFrame
DOMWindow::requestAnimationFrame
where RemoteLayerTreeDrawingArea::flushLayers commit the scrolling state and is actually also called when we perform async scrolling on iOS. So I don't see anything abnormal. Maybe requestAnimationFrame should not commit the scrolling state and let that work be done by the async scrolling code to avoid conflicts?
--
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/20171113/9634d64d/attachment-0001.html>
More information about the webkit-unassigned
mailing list