[css-nav-1] Box tree? Element tree? Fragment tree? etc
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Migrated from https://github.com/WICG/spatial-navigation/issues/47
Originally created by @frivoal on Tue, 03 Apr 2018 07:30:48 GMT
We should do a thorough review of the processing model, to make sure that it consistently and correctly uses the correct tree (element tree vs box tree vs fragment tree...) and the correct ancestry relationships (parent vs containing block).
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 reviewing the CSS Spatial Navigation processing model described in this issue, focusing on where it refers to the element, box, and fragment trees and to parent versus containing-block ancestry. Compare those references for consistency and correctness; done means the model uses the appropriate tree and ancestry relationship throughout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100