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

Issue 2880993004: [LayoutNG] Fixes small crash inside preferred widths. (Closed)

Created:
3 years, 7 months ago by ikilpatrick
Modified:
3 years, 6 months ago
Reviewers:
cbiesinger
CC:
chromium-reviews, ojan+watch_chromium.org, szager+layoutwatch_chromium.org, glebl+reviews_chromium.org, dgrogan+ng_chromium.org, atotic+reviews_chromium.org, blink-reviews-layout_chromium.org, pdr+renderingwatchlist_chromium.org, eae+blinkwatch, leviw+renderwatch, zoltan1, jchaffraix+rendering, blink-reviews
Target Ref:
refs/heads/master
Project:
chromium
Visibility:
Public.

Description

[LayoutNG] Fixes small crash inside preferred widths. We were previously trying to perform perferred width calculation on a non-LayoutNG layout object. BUG=635619 Review-Url: https://codereview.chromium.org/2880993004 Cr-Commit-Position: refs/heads/master@{#480172} Committed: https://chromium.googlesource.com/chromium/src/+/e47fe16501daea54a8926f47a3c9afe778887094

Patch Set 1 #

Patch Set 2 : rebase. #

Total comments: 2

Patch Set 3 : ng-bot expectations. #

Patch Set 4 : ng-bot #

Patch Set 5 : ng-bot2 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+152 lines, -1663 lines) Patch
M third_party/WebKit/LayoutTests/FlagExpectations/enable-blink-features=LayoutNG View 1 2 3 4 346 chunks +143 lines, -1653 lines 0 comments Download
M third_party/WebKit/LayoutTests/TestExpectations View 1 2 3 4 8 chunks +7 lines, -9 lines 0 comments Download
M third_party/WebKit/Source/core/layout/ng/ng_block_node.cc View 1 1 chunk +2 lines, -1 line 0 comments Download

Messages

Total messages: 48 (30 generated)
ianjkilpatrick
3 years, 7 months ago (2017-05-15 16:47:54 UTC) #5
ikilpatrick
3 years, 7 months ago (2017-05-15 16:48:35 UTC) #7
cbiesinger
I'm confused, how do we get to this codepath without NG enabled?
3 years, 7 months ago (2017-05-15 16:51:51 UTC) #8
ikilpatrick
On 2017/05/15 16:51:51, cbiesinger wrote: > I'm confused, how do we get to this codepath ...
3 years, 7 months ago (2017-05-15 17:21:54 UTC) #9
cbiesinger
Can you paste the rest of the stack trace? Basically, I am wondering what calls ...
3 years, 7 months ago (2017-05-15 19:48:06 UTC) #12
ikilpatrick
On 2017/05/15 19:48:06, cbiesinger wrote: > Can you paste the rest of the stack trace? ...
3 years, 7 months ago (2017-05-15 20:45:54 UTC) #13
cbiesinger
Hmm that still ends at NGBlockLayoutAlgorithm... maybe run in a debugger and see where this ...
3 years, 7 months ago (2017-05-15 20:50:08 UTC) #14
ikilpatrick
On 2017/05/15 20:50:08, cbiesinger wrote: > Hmm that still ends at NGBlockLayoutAlgorithm... maybe run in ...
3 years, 6 months ago (2017-06-15 17:31:40 UTC) #15
cbiesinger
lgtm, thanks for the explanation! https://codereview.chromium.org/2880993004/diff/20001/third_party/WebKit/Source/core/layout/ng/ng_block_node.cc File third_party/WebKit/Source/core/layout/ng/ng_block_node.cc (right): https://codereview.chromium.org/2880993004/diff/20001/third_party/WebKit/Source/core/layout/ng/ng_block_node.cc#newcode234 third_party/WebKit/Source/core/layout/ng/ng_block_node.cc:234: return RuntimeEnabledFeatures::LayoutNGEnabled(); Do we ...
3 years, 6 months ago (2017-06-15 17:37:57 UTC) #16
cbiesinger
Also, can we remove some [Crash] expectations now?
3 years, 6 months ago (2017-06-15 17:38:23 UTC) #17
ikilpatrick
On 2017/06/15 17:38:23, cbiesinger wrote: > Also, can we remove some [Crash] expectations now? oh ...
3 years, 6 months ago (2017-06-15 17:40:12 UTC) #18
atotic
On 2017/06/15 at 17:40:12, ikilpatrick wrote: > On 2017/06/15 17:38:23, cbiesinger wrote: > > Also, ...
3 years, 6 months ago (2017-06-15 17:48:15 UTC) #21
ikilpatrick
https://codereview.chromium.org/2880993004/diff/20001/third_party/WebKit/Source/core/layout/ng/ng_block_node.cc File third_party/WebKit/Source/core/layout/ng/ng_block_node.cc (right): https://codereview.chromium.org/2880993004/diff/20001/third_party/WebKit/Source/core/layout/ng/ng_block_node.cc#newcode234 third_party/WebKit/Source/core/layout/ng/ng_block_node.cc:234: return RuntimeEnabledFeatures::LayoutNGEnabled(); On 2017/06/15 17:37:57, cbiesinger wrote: > Do ...
3 years, 6 months ago (2017-06-15 18:05:33 UTC) #22
cbiesinger
On 2017/06/15 18:05:33, ikilpatrick wrote: > https://codereview.chromium.org/2880993004/diff/20001/third_party/WebKit/Source/core/layout/ng/ng_block_node.cc > File third_party/WebKit/Source/core/layout/ng/ng_block_node.cc (right): > > https://codereview.chromium.org/2880993004/diff/20001/third_party/WebKit/Source/core/layout/ng/ng_block_node.cc#newcode234 > ...
3 years, 6 months ago (2017-06-15 18:06:18 UTC) #23
cbiesinger
I guess that's good news and bad news from the bots... * Passed: 35417 (33812 ...
3 years, 6 months ago (2017-06-15 19:52:09 UTC) #26
atotic
On 2017/06/15 at 19:52:09, cbiesinger wrote: > I guess that's good news and bad news ...
3 years, 6 months ago (2017-06-15 21:09:45 UTC) #27
commit-bot: I haz the power
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2880993004/80001
3 years, 6 months ago (2017-06-16 19:53:57 UTC) #45
commit-bot: I haz the power
3 years, 6 months ago (2017-06-16 21:19:40 UTC) #48
Message was sent while issue was closed.
Committed patchset #5 (id:80001) as
https://chromium.googlesource.com/chromium/src/+/e47fe16501daea54a8926f47a3c9...

Powered by Google App Engine
This is Rietveld 408576698