23388 2013-09-28 02:15:53 +0000 Item #4 of the DOM Window Named Item should not allow nor endorse conflation of the name and id namespaces 2016-04-22 18:42:47 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED WONTFIX P2 editorial --- 1 scunliffe.bugzilla robin arronei mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 93989 0 scunliffe.bugzilla 2013-09-28 02:15:53 +0000 From the current draft of the spec http://www.w3.org/html/wg/drafts/html/master/browsers.html#dom-window-nameditem I find item #4 to be out of place and dangerous if implemented and endorsed. "HTML elements that have an id content attribute whose value is name." I've spent the last 12 years of my Web Development career dealing with fixing JavaScript code that incorrectly conflated the ID and NAME namespace causing cross-browser bugs. The ID attribute http://www.w3.org/html/wg/drafts/html/master/dom.html#the-id-attribute is designed as a unique identifier within a document. Whereas a NAME attribute http://www.w3.org/html/wg/drafts/html/master/forms.html#attr-fe-name is designed for naming form controls for HTTP submission and unlike the ID attribute can be duplicated as needed for submitting an Array of values or grouping a set of radio buttons. I fear that acknowledging the bug with Internet Explorer's getElementById(id) and its non-standard document.all collections and actually perpetuating and endorsing it in HTML5 is damaging to the Web. Vague API method/property access implementations are not helpful to the development community and should be avoided at all costs. 126053 1 arronei 2016-04-22 18:42:47 +0000 HTML5.1 Bugzilla Bug Triage: This is handled in this manner for compatibility with the web and browsers. If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!