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 11338 - Add note saying something like "In the HTML serialization, namespace prefixes and namespace declarations are non-conforming and are do not have the same effect as in XML..."
Summary: Add note saying something like "In the HTML serialization, namespace prefixes...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-18 08:30 UTC by contributor
Modified: 2011-08-04 05:00 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2010-11-18 08:30:19 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#namespaces

Comment:
Zeros says we should add a note here saying something like "In the HTML
serialization, namespace prefixes and namespace declarations are
non-conforming and are do not have the same effect as in XML. In particular,
the colon has no special meaning in HTML element names." or some such. 
(depending on what happens with -41, anyway)

Posted from: 98.248.33.53
Comment 1 Elliott Sprehn 2010-11-18 08:39:30 UTC
Zeros = Elliott from the HTML WG.
Comment 2 Aryeh Gregor 2010-11-18 22:17:28 UTC
Namespace prefixes and namespace declarations don't have the same effect in text/html as in XML, but they're conforming in some cases, e.g.,

<!doctype html>
<html xmlns="http://www.w3.org/1999/xhtml">
<title lang=en xml:lang=en>...</title>

validates as HTML5.  The DOM produced here would of course differ between XML and text/html (although this particular example doesn't parse at all as XML).
Comment 3 Ian 'Hixie' Hickson 2010-12-31 04:06:29 UTC
I'll add a note once ISSUE-41 is resolved, if it's resolved in a way that doesn't add xmlns processing.
Comment 4 Ian 'Hixie' Hickson 2011-02-12 00:19:52 UTC
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: Accepted
Change Description: see diff given below
Rationale: I added a note similar to what comment 0 suggests but taking into account comment 2.
Comment 5 contributor 2011-02-12 00:20:39 UTC
Checked in as WHATWG revision r5880.
Check-in comment: add a note that xmlns='' doesn't 'work' in HTML.
http://html5.org/tools/web-apps-tracker?from=5879&to=5880
Comment 6 Michael[tm] Smith 2011-08-04 05:00:46 UTC
mass-moved component to LC1