17195 2012-05-25 19:33:00 +0000 Definition of .properties does not match implementation reality 2013-02-08 01:36:04 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#microdata-dom-api P3 normal Unsorted 1 contributor ian bzbarsky dzbarsky ian mike zcorpan contributor oldest_to_newest 68150 0 contributor 2012-05-25 19:33:00 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html Multipage: http://www.whatwg.org/C#microdata-dom-api Complete: http://www.whatwg.org/c#microdata-dom-api Comment: Definition of .properties does not match implementation reality 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 68151 1 bzbarsky 2012-05-25 19:35:18 +0000 Specifically, this part: The properties IDL attribute on HTML elements must return an HTMLPropertiesCollection rooted at the Document node combined with the fact that all the properties are in the element's home subtree would mean that elements that are not in the document should always have an empty .properties. That doesn't seem to be terribly useful, and as far as I can tell Opera doesn't implement that. Neither does the upcoming Gecko implementation. See upcoming testcase: it would alert 0, then 2, if the spec was actually followed here. In Opera it alerts 1, then 2. 70855 2 contributor 2012-07-18 17:38:02 +0000 This bug was cloned to create bug 18194 as part of operation convergence. 74249 3 ian 2012-09-21 20:09:49 +0000 It's intentional that .properties on elements not in a Document would be empty... not my fault y'all can't follow the spec. :-P 74256 4 ian 2012-09-21 20:16:58 +0000 bz: Do you still have the aforementioned testcase, by any chance? 78812 5 bzbarsky 2012-11-26 05:04:36 +0000 I don't have the testcase anymore, sorry. It was just doing basic testing of what happens in a disconnected subtree. I think the reason people didn't follow the spec as you wrote is threefold: 1) "It doesn't seem to be terribly useful". 2) The action-at-a-distance due to the implications of "rooted at" involving digging up a separate (unlinked, too) spec bit, combined with the fact that actually sharing implementations between HTMLPropertiesCollection and other HTMLCollections didn't happen at least in Gecko for various reasons, so the rooting didn't give behavior for free. 3) Whoever wrote the tests implementors used to verify their implementations didn't follow the spec either. with #3 being likely most important in practice. We could probably change Gecko to do what the spec says if you really think that's a better approach. Why is it better? 78864 6 ian 2012-11-26 20:48:29 +0000 I'm not sure it's really better — I don't really know what it means to be checking for the properties of a node that's not in a Document. But I can root it at the home subtree's root element, or something? I'll have to test to see what implementations actually do. 78876 7 bzbarsky 2012-11-26 22:24:27 +0000 It's worth seeing if Opera is willing to change. I'd really much rather root at the document in Gecko, for what it's worth. Speccing the other is a pain, since the home subtreee's root obviously changes over time. Of course the owner document also changes over time (see adoptNode), so things are a bit annoying no matter what. 78892 8 zcorpan 2012-11-27 05:32:42 +0000 I don't have a strong opinion, but Opera's behavior seems more useful than the spec's. 82725 9 ian 2013-02-08 01:01:24 +0000 http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2086 Gecko and Opera do a remarkable job of implementing what the spec doesn't say, so I guess I'll change the spec to match them... :-) 82726 10 contributor 2013-02-08 01:03:33 +0000 Checked in as WHATWG revision r7705. Check-in comment: Match reality. It's a bit more useful anyway, arguably. http://html5.org/tools/web-apps-tracker?from=7704&to=7705 82728 11 contributor 2013-02-08 01:36:04 +0000 Checked in as WHATWG revision r7706. Check-in comment: Clarify that the collection's root might change during the collection's lifetime. http://html5.org/tools/web-apps-tracker?from=7705&to=7706