This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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
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.
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.
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.
(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.