w3c/csswg-drafts

[css-nav-1] Box tree? Element tree? Fragment tree? etc

Open

#3,359 opened on Dec 3, 2018

View on GitHub
 (0 comments) (1 reaction) (0 assignees)HTML (3,546 stars) (545 forks)batch import
Help Wantedcss-nav-1

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

Tech stack
css
Domain
frontend
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
CSS box modelCSS spatial navigation basicsUnderstanding of element tree
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
5
Research direction
The issue calls for a thorough review of the processing model in the css nav 1 specification. Examine the spec for consistent use of terms like 'element tree', 'box tree', and 'fragment tree', and correct ancestry relationships. Focus on the spatial navigation processing model section and identify inconsistencies. Since there are no comments or PRs, this work is entirely based on the current spec text.