[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..."

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11338

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
            Summary|[Blocked on ISSUE-41] Add   |Add note saying something
                   |note saying something like  |like "In the HTML
                   |"In the HTML serialization, |serialization, namespace
                   |namespace prefixes and      |prefixes and namespace
                   |namespace declarations are  |declarations are
                   |non-conforming and are do   |non-conforming and are do
                   |not have the same effect as |not have the same effect as
                   |in XML..."                  |in XML..."

--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 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.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 12 February 2011 00:19:54 UTC