Bug 126493

Summary: Prepare the ScrollingTree for remote use
Product: WebKit Reporter: Simon Fraser (smfr) <simon.fraser>
Component: New BugsAssignee: Simon Fraser (smfr) <simon.fraser>
Status: RESOLVED FIXED    
Severity: Normal CC: andersca, cmarcelo, commit-queue, eflews.bot, gyuyoung.kim, jamesr, luiz, sam, simon.fraser, thorton, tonikitoo
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch sam: review+, eflews.bot: commit-queue-

Simon Fraser (smfr)
Reported 2014-01-04 13:00:45 PST
Prepare the ScrollingTree for remote use
Attachments
Patch (15.19 KB, patch)
2014-01-04 13:05 PST, Simon Fraser (smfr)
sam: review+
eflews.bot: commit-queue-
Simon Fraser (smfr)
Comment 1 2014-01-04 13:05:17 PST
Sam Weinig
Comment 2 2014-01-04 13:10:23 PST
Comment on attachment 220379 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=220379&action=review > Source/WebCore/page/scrolling/ScrollingStateFixedNode.cpp:76 > + static_cast<GraphicsLayer*>(layer())->syncPosition(position); Should we have some checked casts for this? > Source/WebCore/page/scrolling/ScrollingStateScrollingNode.cpp:79 > // The cloned tree references PlatformLayers, which are safe to send to the scrolling thread. > // FIXME: this Mac threaded-scrolling assumption doesn't belong here. Does this comment still hold? You removed a similar one above. > Source/WebCore/page/scrolling/ScrollingStateStickyNode.cpp:76 > + static_cast<GraphicsLayer*>(layer())->syncPosition(position); Checked cast? > Source/WebCore/page/scrolling/ScrollingStateTree.cpp:201 > +void ScrollingStateTree::setRemovedNodes(const Vector<ScrollingNodeID>& nodes) > +{ > + m_nodesRemovedSinceLastCommit = nodes; > +} Does this do a copy? Can we make it a move? > Source/WebCore/page/scrolling/ScrollingStateTree.cpp:208 > + StateNodeMap::const_iterator it = m_stateNodeMap.find(scrollLayerID); auto?
EFL EWS Bot
Comment 3 2014-01-04 13:10:53 PST
Simon Fraser (smfr)
Comment 4 2014-01-04 13:44:24 PST
Note You need to log in before you can comment on or make changes to this bug.