This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17194 - 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
Summary: It's not clear whether "The HTMLPropertiesCollection interface represents a c...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-25 19:08 UTC by contributor
Modified: 2012-09-01 00:10 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2012-05-25 19:08:55 UTC 
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
Comment 1 Boris Zbarsky 2012-05-25 19:16:01 UTC 
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.
Comment 2 contributor 2012-07-18 17:37:49 UTC 
This bug was cloned to create bug 18193 as part of operation convergence.
Comment 3 Ian 'Hixie' Hickson 2012-09-01 00:08:41 UTC 
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.
Comment 4 contributor 2012-09-01 00:10:28 UTC 
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