-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[container-queries] Stop forcing layout containment but force an independent formatting context #31376
Conversation
EWS run on previous version of this PR (hash a361626) |
Let' start fresh. |
I think I know what's causing most of these failures: This needs to be removed: https://searchfox.org/wubkat/rev/b36cbce69fddb7da33823f316bd8ead5bebee970/Source/WebCore/rendering/RenderElement.cpp#2507-2509 |
a361626
to
a694dd8
Compare
EWS run on previous version of this PR (hash a694dd8)
|
a694dd8
to
5202a1e
Compare
EWS run on previous version of this PR (hash 5202a1e) |
5202a1e
to
3204996
Compare
EWS run on previous version of this PR (hash 3204996) |
houla… what happened. |
d10b0b7
to
66f5a44
Compare
EWS run on previous version of this PR (hash 66f5a44) |
So the tests for table have been fixed, except table-cell tests which still regress. So still 8 FAIL instead of the 16 FAIL initially. |
…pendent formatting context https://bugs.webkit.org/show_bug.cgi?id=277122 rdar://132549134 Reviewed by NOBODY (OOPS!). container-type does not force layout containment, but does force an independent formatting context by CSS WG resolution on w3c/csswg-drafts#10544 This takes into account the latest import for container queries WPT tests formatting web-platform-tests/wpt@27c89c6 * LayoutTests/TestExpectations: * Source/WebCore/rendering/RenderBlock.cpp: (WebCore::RenderBlock::firstLineBaseline const): * Source/WebCore/rendering/RenderElement.cpp: (WebCore::RenderElement::establishesIndependentFormattingContext const): (WebCore::RenderElement::hasEligibleContainmentForSizeQuery const): * Source/WebCore/rendering/style/StyleRareNonInheritedData.cpp: (WebCore::StyleRareNonInheritedData::usedContain const): Co-authored-by: Tim Nguyen <ntim@apple.com>
66f5a44
to
9c47b8d
Compare
EWS run on current version of this PR (hash 9c47b8d) |
@bfgeek |
@karlcow @alanbaradlay - The zero table-cell + baseline isn't particularly important to the test (IMO). If you like we can just change that test (to use Thougths? |
I agree that it's not super important. I could also just skip the test temporarily until after I address the baseline bug. Let's see if I can get to it in the next couple of days, if not, I'll land this one way or another. |
As pointed out in: WebKit/WebKit#31376 (comment) Blink/WebKit were doing something incorrect when a baseline was outside the border-box of a flex-item. This was because we were initializing max_major_descent and max_minor_descent to zero, instead of LayoutUnit::Min(), (similar to FlexLine::max_major_ascent_ FlexLine::max_minor_ascent_). This only occurs with a single item in a flex-line. Change-Id: I4f32eb912a07247d16231451ba63e7c7a75a8b23
As pointed out in: WebKit/WebKit#31376 (comment) Blink/WebKit were doing something incorrect when a baseline was outside the border-box of a flex-item. This was because we were initializing max_major_descent and max_minor_descent to zero, instead of LayoutUnit::Min(), (similar to FlexLine::max_major_ascent_ FlexLine::max_minor_ascent_). This only occurs with a single item in a flex-line. Change-Id: I4f32eb912a07247d16231451ba63e7c7a75a8b23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5901280 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1363827}
As pointed out in: WebKit/WebKit#31376 (comment) Blink/WebKit were doing something incorrect when a baseline was outside the border-box of a flex-item. This was because we were initializing max_major_descent and max_minor_descent to zero, instead of LayoutUnit::Min(), (similar to FlexLine::max_major_ascent_ FlexLine::max_minor_ascent_). This only occurs with a single item in a flex-line. Change-Id: I4f32eb912a07247d16231451ba63e7c7a75a8b23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5901280 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1363827}
As pointed out in: WebKit/WebKit#31376 (comment) Blink/WebKit were doing something incorrect when a baseline was outside the border-box of a flex-item. This was because we were initializing max_major_descent and max_minor_descent to zero, instead of LayoutUnit::Min(), (similar to FlexLine::max_major_ascent_ FlexLine::max_minor_ascent_). This only occurs with a single item in a flex-line. Change-Id: I4f32eb912a07247d16231451ba63e7c7a75a8b23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5901280 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1363827}
This is fixed by e0a7770 |
…ith extreme baselines., a=testonly Automatic update from web-platform-tests [flex] Fix line cross-size calculation with extreme baselines. As pointed out in: WebKit/WebKit#31376 (comment) Blink/WebKit were doing something incorrect when a baseline was outside the border-box of a flex-item. This was because we were initializing max_major_descent and max_minor_descent to zero, instead of LayoutUnit::Min(), (similar to FlexLine::max_major_ascent_ FlexLine::max_minor_ascent_). This only occurs with a single item in a flex-line. Change-Id: I4f32eb912a07247d16231451ba63e7c7a75a8b23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5901280 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1363827} -- wpt-commits: a860f3bee0f0c23461759e009149d36377c894ad wpt-pr: 48453
…ith extreme baselines., a=testonly Automatic update from web-platform-tests [flex] Fix line cross-size calculation with extreme baselines. As pointed out in: WebKit/WebKit#31376 (comment) Blink/WebKit were doing something incorrect when a baseline was outside the border-box of a flex-item. This was because we were initializing max_major_descent and max_minor_descent to zero, instead of LayoutUnit::Min(), (similar to FlexLine::max_major_ascent_ FlexLine::max_minor_ascent_). This only occurs with a single item in a flex-line. Change-Id: I4f32eb912a07247d16231451ba63e7c7a75a8b23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5901280 Commit-Queue: Ian Kilpatrick <ikilpatrickchromium.org> Reviewed-by: David Grogan <dgroganchromium.org> Cr-Commit-Position: refs/heads/main{#1363827} -- wpt-commits: a860f3bee0f0c23461759e009149d36377c894ad wpt-pr: 48453 UltraBlame original commit: b4bd4104b815edf9525ea3f33cfd841a7149942a
…ith extreme baselines., a=testonly Automatic update from web-platform-tests [flex] Fix line cross-size calculation with extreme baselines. As pointed out in: WebKit/WebKit#31376 (comment) Blink/WebKit were doing something incorrect when a baseline was outside the border-box of a flex-item. This was because we were initializing max_major_descent and max_minor_descent to zero, instead of LayoutUnit::Min(), (similar to FlexLine::max_major_ascent_ FlexLine::max_minor_ascent_). This only occurs with a single item in a flex-line. Change-Id: I4f32eb912a07247d16231451ba63e7c7a75a8b23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5901280 Commit-Queue: Ian Kilpatrick <ikilpatrickchromium.org> Reviewed-by: David Grogan <dgroganchromium.org> Cr-Commit-Position: refs/heads/main{#1363827} -- wpt-commits: a860f3bee0f0c23461759e009149d36377c894ad wpt-pr: 48453 UltraBlame original commit: b4bd4104b815edf9525ea3f33cfd841a7149942a
…ith extreme baselines., a=testonly Automatic update from web-platform-tests [flex] Fix line cross-size calculation with extreme baselines. As pointed out in: WebKit/WebKit#31376 (comment) Blink/WebKit were doing something incorrect when a baseline was outside the border-box of a flex-item. This was because we were initializing max_major_descent and max_minor_descent to zero, instead of LayoutUnit::Min(), (similar to FlexLine::max_major_ascent_ FlexLine::max_minor_ascent_). This only occurs with a single item in a flex-line. Change-Id: I4f32eb912a07247d16231451ba63e7c7a75a8b23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5901280 Commit-Queue: Ian Kilpatrick <ikilpatrickchromium.org> Reviewed-by: David Grogan <dgroganchromium.org> Cr-Commit-Position: refs/heads/main{#1363827} -- wpt-commits: a860f3bee0f0c23461759e009149d36377c894ad wpt-pr: 48453 UltraBlame original commit: b4bd4104b815edf9525ea3f33cfd841a7149942a
9c47b8d
9c47b8d