Bug 306830
| Summary: | [css-anchor-position-1] Interpret position-try-order logical axis using the containing block's writing mode | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | fantasai <fantasai.bugs> |
| Component: | CSS | Assignee: | Kiet Ho <kiet.ho> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | fantasai.bugs, kiet.ho, koivisto, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Local Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=310959 | ||
| Bug Depends on: | |||
| Bug Blocks: | 289743, 291856 | ||
fantasai
Currently we use the box's own writing mode to resolve position-try-order values, but the spec was updated to use the containing block writing mode.
See https://github.com/w3c/csswg-drafts/issues/12869#issuecomment-3406959070
and https://wpt.live/css/css-anchor-position/position-try-order-logical.html
The relevant code lives in TreeResolver::sortPositionOptionsIfNeeded() ; should be an easy fix.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/169501069>
Kiet Ho
Note that there are actually two parts to this: position-try-options and position-try-fallbacks both got switched to use the containing block's writing mode.
Kiet Ho
[css-anchor-position-1] position-try-fallbacks tactic keywords should be resolved against the containing block's writing mode
https://bugs.webkit.org/show_bug.cgi?id=310959
Kiet Ho
Pull request: https://github.com/WebKit/WebKit/pull/61558
EWS
Committed 310277@main (121963fe3074): <https://commits.webkit.org/310277@main>
Reviewed commits have been landed. Closing PR #61558 and removing active labels.