W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > May 2011

[Bug 12602] "<select><option>\n<option></select>" isn't a placeholder label option because its value is "\n", which is silly. We should strip spaces from the start and end in the definition of the option's label when it comes from textContent.

From: <bugzilla@jessica.w3.org>
Date: Tue, 10 May 2011 04:59:07 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QJf2J-0006OJ-4h@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12602

--- Comment #2 from Michael(tm) Smith <mike@w3.org> 2011-05-10 04:59:06 UTC ---
(In reply to comment #1)
> This is easy to work around

It's not so much the problem how to work around it, but instead what the
document-conformance criteria should be for the general case of documents that
contain value-less <select required><option>\s+</option></select> (where \s+ is
one or more space, tab, LF, FF, or CR characters).

The spec as currently worded makes that invalid (and conformance checkers have
to report it as an error) because the "value" of the option is considered
non-empty, because (technically) the text content of the option is non-empty.

So the change this bug describes it to make the "value" of a
value-attribute-less option be considered non-empty only if the text content of
the option is non-empty after leading and trailing space characters are
stripped from it. (And fwiw, the validator.nu check for this was implemented
that way, with the anticipation that this change will get made to the spec.)

-- 
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 Tuesday, 10 May 2011 04:59:12 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:10 UTC