oddbird / oddbird/css-anchor-positioning
Use Layout/Box tree order instead of DOM Tree order
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 493
- Forks
- 18
- Avg merge
- 12h 37m
- Merged PRs (30d)
- 5
Description
Per @mfreed7- " What matters is that the anchor element gets laid out first, and the anchored/positioned element gets laid out after that."
DOM and Layout/Box tree order are quite similar, but aren't identical. For a counter example, see https://github.com/web-platform-tests/wpt/blob/master/css/css-anchor-position/anchor-position-top-layer-005.html.
https://github.com/oddbird/css-anchor-positioning/pull/207
Related:
-
https://github.com/oddbird/css-anchor-positioning/issues/103#issuecomment-2197293946
-
Unskip test from 5ab4ea406916fbe44edcca66c312fa863bf698d0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading pull request #207, the linked WPT case css/css-anchor-position/anchor-position-top-layer-005.html, and the change associated with commit 5ab4ea406916fbe44edcca66c312fa863bf698d0. Determine where the polyfill uses DOM order instead of Layout/Box tree order, then verify the fix by unskipping the named test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100