W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2011

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

From: <bugzilla@jessica.w3.org>
Date: Thu, 29 Sep 2011 01:50:33 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1R95lh-0004gK-QJ@jessica.w3.org>

Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:

           What    |Removed                     |Added
           Keywords|                            |a11y

--- Comment #17 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-09-29 01:50:33 UTC ---
(In reply to comment #16)
> All that sounds like browsers' word-breaking/find/etc. being buggy.  It doesn't
> justify making markup like this invalid.

Well, you used as argument that two browsers support the suggested behaviour.
Since that is not true -  since the presense of mark-up  in every user agent
tested, has at least one situation wehre an composed character that has been
"split up" with mark-up, become interpreted as separated characters - one
cannot use that as argument either.

But I agree that there is nothing wrong with mark-up around graphes, per se, if
it would not have these side effects. (The very thing that such mark-up could
affect normalization, does not sound convincing tomyself.) My main issue is
that browsers have a road ahead of them when it comes to properly implement

Btw, my objection to this being legal, is similar to my sceptisism towards the
<wbr> tag: The <wbr> tag too has the effect of making words be treated as
separate words, but without the authors proper awareness of the effect.

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, 29 September 2011 01:50:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:04 UTC