W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2010

[Bug 9965] White space in attributes - please justify why multiple spaces/linebreaks are problematic - or delete this requirement

From: <bugzilla@jessica.w3.org>
Date: Mon, 21 Jun 2010 08:32:27 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1OQcQd-0002eA-PT@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9965


Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hsivonen@iki.fi




--- Comment #1 from Henri Sivonen <hsivonen@iki.fi>  2010-06-21 08:32:27 ---
(In reply to comment #0)
> These are handled inconsistently by user agents.
[...]
> However, I believe that this is not any problem any more. At least I have not
> heard about it as a text/html problem. So I think this req should be deleted.

The polyglot publication should not be based on beliefs about what user agents
do. Doing that would just get us another Appendix C. It should be based on
logical inferences from the normative statements in HTML5, XML, Namespaces in
XML and the DOM.

The correct thing to say here is:
Tabs, line feeds and carriage returns in attribute values must be encoded as
numeric character references. At least every second of consecutive spaces in
attribute values must be encoded as numeric character references (so that there
are no consecutive literal spaces in attribute values). This is because XML
parsing doesn't preserve unescaped tabs, line feeds, carriage returns or
consecutive spaces in attribute values.

-- 
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 Monday, 21 June 2010 08:32:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 21 June 2010 08:32:32 GMT