W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2017

[Bug 30119] 'COMMAND' element as HTML element

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Jun 2017 02:39:30 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30119-523-08Pi3rILlw@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30119

Liam R E Quin <liam@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |liam@w3.org

--- Comment #8 from Liam R E Quin <liam@w3.org> ---
I don't see this as a significant interoperability issue.

A smart implementation would probably have a configurable list of elements to
be serialized as empty, and attributes to be quoted, I suppose.

For the now, since command isn't in HTML, it should be fine to serialize it in
HTML style when it's empty and you're generating HTML 5, and quoting the
attribute isn't going to hurt either. Not doing those things also isn't a
problem, since the element isn't implemented in HTML agents. So it doesn't seem
worth expecting implementations to change, and deleting the tests doesn't sound
like a bad idea to me.

It probably should not be an error to have a non-empty element called command,
although it would also (arguably) be unwise as there may well be HTML agents
that *do* recognize it as a "null" (EMPTY) element and including it in HTML
files could therefore lead to really obscure interoperability problems.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 20 June 2017 02:39:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 June 2017 02:39:38 UTC