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 8235 - 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.
Summary: Given that Gecko and Webkit don't support them in XML, I think that named pro...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: NE
Depends on:
Blocks:
 
Reported: 2009-11-07 22:05 UTC by contributor
Modified: 2010-10-04 13:55 UTC (History)
7 users (show)

See Also:

Attachments

Description contributor 2009-11-07 22:05:43 UTC 
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
Comment 1 Boris Zbarsky 2009-11-08 18:01:02 UTC 
Note that Gecko has added (or is about to add; not sure whether he patch has landed yet) support for these in XHTML documents.
Comment 2 Ian 'Hixie' Hickson 2010-01-05 06:27:04 UTC 
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
Comment 3 Boris Zbarsky 2010-01-05 12:10:10 UTC 
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.
Comment 4 Maciej Stachowiak 2010-01-05 14:40:10 UTC 
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.