Closed Bug 1874110 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 43936 - [css-anchor-position] Implement new inset-area proposal

Categories

(Core :: CSS Parsing and Computation, task, P4)

Product:
Core
Component:
CSS Parsing and Computation
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
123 Branch
Tracking Flags:
Tracking Status
firefox123 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 43936 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/43936
Details from upstream follow.

Rune Lillesveen <futhark@chromium.org> wrote:

[css-anchor-position] Implement new inset-area proposal

The new proposal is here:

https://github.com/w3c/csswg-drafts/issues/9598#issuecomment-1836854109

inset-area now affects the containing block size and 'auto' insets
become 0 for inset-area.

Bug: 1477314

Change-Id: Ia2f0d5a1f866cd659f9e3f87ec2f639141df6a94
Reviewed-on: https://chromium-review.googlesource.com/5163733
WPT-Export-Revision: c13ac612d73afed1465d465f8b431dd94a9fae9b

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests

Status Summary

Firefox

FAIL: 2

Chrome

PASS: 1
FAIL: 1

Safari

FAIL: 2

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/80bea1dc6b12 [wpt PR 43936] - [css-anchor-position] Implement new inset-area proposal, a=testonly https://hg.mozilla.org/integration/autoland/rev/e4731a0e3be0 [wpt PR 43936] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/80bea1dc6b12
https://hg.mozilla.org/mozilla-central/rev/e4731a0e3be0

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox123: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in before you can comment on or make changes to this bug.