17194 2012-05-25 19:08:55 +0000 It's not clear whether "The HTMLPropertiesCollection interface represents a collection of elements that add name-value pairs to a particular item in the microdata model." is a normative requirement 2012-09-01 00:10:28 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#htmlpropertiescollection-0 P3 normal Unsorted 1 contributor ian bzbarsky dzbarsky ian mike contributor oldest_to_newest 68148 0 contributor 2012-05-25 19:08:55 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html Multipage: http://www.whatwg.org/C#htmlpropertiescollection-0 Complete: http://www.whatwg.org/c#htmlpropertiescollection-0 Comment: It's not clear whether "The HTMLPropertiesCollection interface represents a collection of elements that add name-value pairs to a particular item in the microdata model." is a normative requirement Posted from: 71.184.125.56 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/15.0 Firefox/15.0a1 68149 1 bzbarsky 2012-05-25 19:16:01 +0000 To expand on this: It looks like a non-normative thing because of "a collection" vs "the collection". But "represents" is a technical term for collections: it determines the exact set of names and ids that the collection has. So if this is a non-normative statement, then we should not use "represents" here, ideally. On the other hand, if this requirement is normative, then I'm not sure what it's supposed to mean, exactly. And specifically, what should the .properties be for an element not in a document? If I ignore this statement, the spec currently says empty collection. 70853 2 contributor 2012-07-18 17:37:49 +0000 This bug was cloned to create bug 18193 as part of operation convergence. 73132 3 ian 2012-09-01 00:08:41 +0000 Yikes, yeah, that's bad wording. Fixed. Empty collection for out-of-doc elements is right: an element can't get properties from elements outside its home subtree, and the e.properties collection's filter is always rooted to a Document, so there's no way for an element outside the document to have properties in the document's subtree. 73133 4 contributor 2012-09-01 00:10:28 +0000 Checked in as WHATWG revision r7307. Check-in comment: Clean up the Collections section, e.g. avoid the normatively-significant word 'represents'. http://html5.org/tools/web-apps-tracker?from=7306&to=7307