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.