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

[Bug 11526] newlines in attribute values

From: <bugzilla@jessica.w3.org>
Date: Mon, 13 Dec 2010 12:32:21 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PS7Zl-0005qx-D6@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11526

--- Comment #3 from David Carlisle <davidc@nag.co.uk> 2010-12-13 12:32:21 UTC ---
(In reply to comment #1)
> While I agree that in this case the DOM difference does no harm, relaxing the
> goal from "identical" to "compatible" is a definitional slippery slope.


one stated goal of polyglot documents though is allow the xml toolchain to be
used to generate documents served as text/html. Most SVG tools are going to
wrap the long svg path attributes as xml normalisation and/or svg white space
rules mean that it is safe for them to do so.

thus not allowing newlines here just to obtain an identical dom seems
optimising for a non-use case (the number of times when you are going to want
to serve the same thing with two different mime types and have identical white
space in attributes must be vanishingly small) while preventing one of the main
aims of the specification (allowing you to generate xhtml+svg+mathml documents
served as text/html in a safe way.

I think that I'd say don't put newlines in the title attribute, or attributes
holding URI, but allow them elsewhere, noting in the introduction that white
space differences in attributes are ignored except as noted in the body of the
specification.

-- 
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, 13 December 2010 12:32:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:35 UTC