Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1184)

Issue 1945353002: [Layout API] Start converting ScrollAnchor to new layout API (Closed)

Created:
4 years, 7 months ago by pilgrim_google
Modified:
4 years, 7 months ago
CC:
blink-reviews, blink-reviews-layout_chromium.org, chromium-reviews, eae+blinkwatch, jchaffraix+rendering, leviw+renderwatch, pdr+renderingwatchlist_chromium.org, szager+layoutwatch_chromium.org, zoltan1, dgrogan
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

[Layout API] Start converting ScrollAnchor to new layout API There were several references to a static method, scrollerLayoutBox, which returns a raw LayoutBox*, which is deprecated by the new layout API. I can't convert all the references at once because there is a long chain of reference passing to unwind, so I (TEMPORARILY) duplicated the method to create scrollerLayoutBoxItem() and started converting the easy references to use that instead. There are no functional changes. BUG=499321 Committed: https://crrev.com/a313736960ccd0293046b192a3ea41aa4d2ae78f Cr-Commit-Position: refs/heads/master@{#391522}

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+23 lines, -6 lines) Patch
M third_party/WebKit/Source/core/frame/FrameView.h View 2 chunks +6 lines, -5 lines 0 comments Download
M third_party/WebKit/Source/core/layout/ScrollAnchor.cpp View 3 chunks +12 lines, -1 line 0 comments Download
M third_party/WebKit/Source/core/layout/api/LayoutBoxItem.h View 1 chunk +5 lines, -0 lines 0 comments Download

Messages

Total messages: 12 (4 generated)
pilgrim_google
4 years, 7 months ago (2016-05-04 14:34:42 UTC) #2
eae
+skobes so that he's aware of the effort LGTM
4 years, 7 months ago (2016-05-04 14:37:31 UTC) #4
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1945353002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1945353002/1
4 years, 7 months ago (2016-05-04 14:53:27 UTC) #6
skobes
I'm confused. I thought core/layout/api was for consumption by things outside of layout? Why would ...
4 years, 7 months ago (2016-05-04 15:50:39 UTC) #7
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years, 7 months ago (2016-05-04 15:57:03 UTC) #8
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/a313736960ccd0293046b192a3ea41aa4d2ae78f Cr-Commit-Position: refs/heads/master@{#391522}
4 years, 7 months ago (2016-05-04 15:58:07 UTC) #10
pilgrim_google
On 2016/05/04 at 15:50:39, skobes wrote: > I'm confused. I thought core/layout/api was for consumption ...
4 years, 7 months ago (2016-05-04 16:23:22 UTC) #11
skobes
4 years, 7 months ago (2016-05-04 16:35:38 UTC) #12
Message was sent while issue was closed.
On 2016/05/04 16:23:22, pilgrim_google wrote:
> On 2016/05/04 at 15:50:39, skobes wrote:
> > I'm confused.  I thought core/layout/api was for consumption by things
outside
> of layout?  Why would ScrollAnchor need to use it?
> 
> Because it's using a method on FrameView that returns a raw LayoutBox*, and
I'm
> trying to get rid of that method.

Hmm ok.  Sounds like root layer scrolling may improve this.  Will a
PaintLayerScrollableArea still be able to provide its LayoutBox*?

Powered by Google App Engine
This is Rietveld 408576698