w3c/csswg-drafts

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

Open

#3,359 建立於 2018年12月3日

在 GitHub 查看
 (0 留言) (1 反應) (0 負責人)HTML (3,546 star) (545 fork)batch import
Help Wantedcss-nav-1

描述

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).

貢獻者指南

技術棧
css
領域
frontend
議題類型
research
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
CSS box modelCSS spatial navigation basicsUnderstanding of element tree
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
5
研究方向
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.
[css-nav-1] Box tree? Element tree? Fragment tree? etc · w3c/csswg-drafts#3359 | Good First Issue