- From: <bugzilla@jessica.w3.org>
- Date: Mon, 26 Sep 2011 22:14:18 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13502 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #9 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-09-26 22:14:18 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: see diff below Rationale: I've explicitly made the spec disallow isolated combining characters. If the use case is just colouring accents, then IMHO CSS should support that directly. It doesn't make any sense to style different parts of a combined character differently, since per Unicode, there is only one grapheme cluster involved; indeed, there might only be one glyph from the font being rendered, e.g. if the combination corresponds to a precomposed character, or if a ligature exists for that combination. (The question of how such things should render is a CSS one.) -- 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 Monday, 26 September 2011 22:14:22 UTC