- From: <bugzilla@jessica.w3.org>
- Date: Thu, 30 Sep 2010 02:39:52 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10838 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ian@hixie.ch Resolution| |WONTFIX --- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-30 02:39:51 UTC --- 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: If we introduced <u> with the semantic "proper name mark", it would just be used incorrectly by everyone. So doing that would be bad. If this is a use case that we should address, then we're better off introducing a new element for it. I can't find another reason to have <u> (I've thought about this quite a bit). It really does seem to be purely presentational; far more than even <small>, <b>, <i>, and <s>. -- 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 Thursday, 30 September 2010 02:39:56 UTC