"determine the value of a named property" should not imply a new object each time · whatwg/html#5266

(11 comments) (0 reactions) (0 assignees)HTML (7,654 stars) (2,520 forks)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
Issue 種別: documentation
難度: 3
推定時間: half day
活動状況: stale
明確さ: clear
前提条件: なし
初心者向け度: 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.