- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 23 Feb 2010 10:58:59 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9048
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-02-23 10:58:59 ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
http://dev.w3.org/html5/decision-policy/decision-policy.html
Status: Rejected
Change Description: no spec change
Rationale: Yeah, I considered that. I also considered "The content attribute
must be specified unless the charset attribute is specified, in which case it
must be omitted". However, upon comparing the three, I came to the conclusion
they were all pretty confusing. The one in the spec is the only one that
clearly makes the link between the attributes that need content="" and the
content="" attribute, rather than linking content="" specifically to the one
attribute that _doesn't_ need it (charset=""), which seemed to be a slight win.
--
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, 23 February 2010 10:59:01 UTC