24665 2014-02-14 19:34:33 +0000 htmlFor is a "DOMSettableTokenList" interface. Shouldn't it be a "Elements" collection? 2014-02-20 21:49:19 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-output-element P3 normal Unsorted 1 contributor ian anakin_rendine ian mike contributor oldest_to_newest 100611 0 contributor 2014-02-14 19:34:33 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html Multipage: http://www.whatwg.org/C#the-output-element Complete: http://www.whatwg.org/c#the-output-element Referrer: Comment: htmlFor is a "DOMSettableTokenList" interface. Shouldn't it be a "Elements" collection? Posted from: 78.13.40.15 User agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.107 Safari/537.36 100624 1 ian 2014-02-14 21:18:47 +0000 We don't have an existing elaborate interface mechanism for adding and removing elements by reference and having it update a space-separated list of IDs. Developing one just for this obscure feature doesn't seem worth it. 100673 2 anakin_rendine 2014-02-15 11:16:54 +0000 I thought it would be as easy as creating a reference to a form control from a label using the @for attribute defined on <label>, only with a collection of elements. 101013 3 ian 2014-02-20 20:47:44 +0000 The difference is that <output for> is a list of IDs, whereas <label for> is just one ID. Also, <label> doesn't have a mutable API for setting the for="" attribute via an element either. 101040 4 anakin_rendine 2014-02-20 21:49:19 +0000 (In reply to Ian 'Hixie' Hickson from comment #3) > The difference is that <output for> is a list of IDs, whereas <label for> is > just one ID. Also, <label> doesn't have a mutable API for setting the for="" > attribute via an element either. Mutability IS a serious issue. This solves everything and the fact that the list is anyway available can be exploited somehow. Thank you.