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 (545 forks)batch import
Help Wantedcss-nav-1

Repository metrics

Stars
 (3,546 stars)
PR merge metrics
 (Avg merge 87d 7h) (24 merged PRs in 30d)

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

Research direction
Review the CSS Navigation specification and identify all occurrences of terms like 'element tree', 'box tree', 'fragment tree'. Ensure that each usage is correct and consistent with the CSS specifications.
Tech stack
None
Domain
documentation
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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.
Mostly clear
Prerequisites
CSS spec understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30