- From: <bugzilla@jessica.w3.org>
- Date: Fri, 17 Sep 2010 18:01:36 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10380
Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|"the content attribute must |Description of IDL sets for
|be set to the conforming |enumerated attributes does
|value associated with the |not appear to match reality
|state that the attribute |
|would be in if set to the |
|given new value". Does |
|this imply in canonical |
|case? Browsers seem to |
|preserve the case when you |
|do an IDL set. This |
Summary|alert |
--- Comment #2 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2010-09-17 18:01:35 ---
The simple way to fix this would be to just change
"""
on setting, if the new value is an ASCII case-insensitive match for one of the
keywords given for that attribute, then the content attribute must be set to
the conforming value associated with the state that the attribute would be in
if set to the given new value, otherwise, if the new value is the empty string,
then the content attribute must be removed, otherwise, the content attribute
must be set to the given new value.
"""
to
"""
on setting, the content attribute must be set to the given new value.
"""
This seems to match what browsers do a lot more closely. I don't notice
browsers implementing the magic behavior required for the empty string, either.
--
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 Friday, 17 September 2010 18:01:37 UTC