Closed Bug 1823833 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 39133 - [anchor-position] Resolve anchor functions in getComputedStyle()

Categories

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

task

Tracking

()

RESOLVED FIXED
114 Branch
Tracking Status
firefox114 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Xiaocheng Hu <xiaochengh@chromium.org> wrote:

[anchor-position] Resolve anchor functions in getComputedStyle()

Currently, when getComputedStyle() returns values for left etc,
it needs to re-resolve them (after layout) into a pixel value.

This patch provides an NGAnchorEvaluatorImpl for the resolution, so
that anchor functions can also be resolved.

There are also a few cases that are unsolved and left for future.
They are marked with TODOs.

Fixed: 1423493
Change-Id: I319543230008e61a8363fdebb111a9840adc6e5d

Reviewed-on: https://chromium-review.googlesource.com/4330385
WPT-Export-Revision: 54a8ee9be53121f266db10bba8bd5804927a2a52

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

CI Results

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

Total 1 tests and 3 subtests

Status Summary

Firefox

OK : 1
FAIL: 3

Chrome

OK : 1
FAIL: 3

Safari

OK : 1
FAIL: 3

Links

Gecko CI (Treeherder)
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/2fa547ffe831 [wpt PR 39133] - [anchor-position] Resolve anchor functions in getComputedStyle(), a=testonly https://hg.mozilla.org/integration/autoland/rev/5b6b98aa68ab [wpt PR 39133] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
You need to log in before you can comment on or make changes to this bug.