[Bug 13502] Text run starting with composing character should be valid

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13502

Aryeh Gregor <ayg@aryeh.name> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |

--- Comment #11 from Aryeh Gregor <ayg@aryeh.name> 2011-09-27 00:24:54 UTC ---
Test case:

data:text/html,<!doctype html>
<span style=font-size:7em>
<span style=color:blue>&%23x05de;</span>&%23x0592;
&%23x05de;&%23x0592;
</span>

In both Firefox 8.0a2 and Chrome 15 dev on Ubuntu 11.04, this displays two
identical grapheme clusters.  The base glyph in the first (right-hand) blue
while the associated diacritic is black, but the display is otherwise
unaffected, exactly as desired.  Opera 11.50 displays the diacritic in the
first cluster as a box, refusing to combine it with the different-colored
character.

This demonstrates that two major browsers already behave as desired in the
cases we're interested in.  It's useful functionality, and there's no reason
for the spec to make it invalid.  It might be that there are some cases where
styling the diacritic differently from the base character makes no sense, but
in some cases it does -- don't throw out the baby with the bathwater.  If you
can identify specific markup that definitely doesn't make sense, make that
specific markup invalid.

What does "If the use case is just colouring accents, then IMHO CSS should
support that directly" mean?  I gave two real-world use-cases in comment 8, and
both of them require being able to style some diacritics on a letter
differently than others.  A CSS property like diacritic-color or whatever would
not serve the use-cases.  It has to be possible to identify individual
diacritics to style, and the only way to do that is to put tags in the markup.

-- 
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, 27 September 2011 00:24:58 UTC