Closed Bug 1934594 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 49464 - TransformPositionArea() incorrectly assumed two-value input

Categories

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

task

Tracking

()

RESOLVED FIXED
135 Branch
Tracking Status
firefox135 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Rune Lillesveen <futhark@chromium.org> wrote:

TransformPositionArea() incorrectly assumed two-value input

Crashed when input was not a pair, but assumed it would be.

For logical values like position-area:start, we can store the value as
a single keyword, but the flip-block version of it needs to be two
separate values.

position-area might be represented as a single keyword depending on
which it is, but it's irrelevant whether the non-flipped value was a
single keyword or two keywords. For simplicity keep identical values.

Bug: 380321441
Change-Id: I29b91e7cc6dd7bea286f11475382117afb872377
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6063638
Reviewed-by: Anders Hartvoll Ruud \<andruud@chromium.org>
Commit-Queue: Rune Lillesveen \<futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1390298}

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

CI Results

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

Total 1 tests

Status Summary

Firefox

PASS : 1

Chrome

CRASH: 1

Safari

PASS : 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9cf78c1064af [wpt PR 49464] - TransformPositionArea() incorrectly assumed two-value input, a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
You need to log in before you can comment on or make changes to this bug.