8235 2009-11-07 22:05:43 +0000 Given that Gecko and Webkit don't support them in XML, I think that named properties in HTMLDocument objects should be restricted to HTML documents, given that this feature is only included for backward compatibility and is horribly designed. 2010-10-04 13:55:13 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#dom-tree-accessors NE P3 normal LC 1 contributor ian bzbarsky ian mike mjs public-html-admin public-html-wg-issue-tracking scampa.giovanni public-html-bugzilla oldest_to_newest 29444 0 contributor 2009-11-07 22:05:43 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#dom-tree-accessors Comment: Given that Gecko and Webkit don't support them in XML, I think that named properties in HTMLDocument objects should be restricted to HTML documents, given that this feature is only included for backward compatibility and is horribly designed. Posted from: 80.180.95.149 29459 1 bzbarsky 2009-11-08 18:01:02 +0000 Note that Gecko has added (or is about to add; not sure whether he patch has landed yet) support for these in XHTML documents. 30446 2 ian 2010-01-05 06:27:04 +0000 bz: do you think this bug should be wontfixed, then? (I can see arguments both ways — remove them because it encourages bad authoring, keep them to enable transition to XHTML.) I'm happy to have the spec say whatever implementations are going to do here. Any advice from implementors on what to do would be very welcome. EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: awaiting further advice as noted above 30529 3 bzbarsky 2010-01-05 12:10:10 +0000 I don't know which way we want to go here spec-wise; for now Gecko alphas have aligned with the spec as written in https://bugzilla.mozilla.org/show_bug.cgi?id=340017 and we'll see how that goes. 30532 4 mjs 2010-01-05 14:40:10 +0000 For WebKit we're willing to go either way. It would be simpler to make behavior the same, but on the other hand catchall behavior on the document creates needless potential for namespace collisions, so it would be kind of nice to avoid it where it's not needed.