whatwg/html

"determine the value of a named property" should not imply a new object each time

Open

#5,266 建立於 2020年2月10日

在 GitHub 查看
 (11 留言) (0 反應) (0 負責人)HTML (7,654 star) (2,520 fork)batch import
good first issueneeds teststopic: forms

描述

Some people seem to read https://html.spec.whatwg.org/multipage/forms.html#dom-form-nameditem as implying that a new nodelist should be returned each time when there are multiple matching elements. That's not the intent, I assume, and it might be worth clarifying the spec to make it clear.

All browsers I tested (Firefox, Chrome, Safari) return the same nodelist on multiple accesses.

貢獻者指南

技術棧
html
領域
documentation
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
無
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The issue calls for clarifying the spec text in the HTML Standard, specifically the 'determine the value of a named property' algorithm in the forms section. The key point is that browsers return the same NodeList object on multiple accesses, so the spec should explicitly state that a new object is not expected. The resolution might involve adding a note or changing the wording in the algorithm. See the referenced section at https://html.spec.whatwg.org/multipage/forms.html#dom form nameditem.