W3C home > Mailing lists > Public > www-validator-cvs@w3.org > April 2013

[Bug 12400] Inconsistent treatment of combining characters beginning text run

From: <bugzilla@jessica.w3.org>
Date: Sun, 21 Apr 2013 06:37:24 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-12400-169-WXGowc36no@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12400

Shai Berger <shai@platonix.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                URL|http://webkeys.platonix.co. |http://webkeys.platonix.co.
                   |il/show/si1452/             |il/layouts/show/system/si14
                   |                            |52/
           See Also|                            |https://www.w3.org/Bugs/Pub
                   |                            |lic/show_bug.cgi?id=13502
         Resolution|WORKSFORME                  |---

--- Comment #2 from Shai Berger <shai@platonix.com> ---
Since this bug was filed, several things changed. One of them is the page URL
(updated). Another is that the issue was discussed in #13502 (added as "see
also"), where it was concluded that both the use case (a combined character
with separate styling for the separate parts) and the implementation (a text
run starting with a combining character) are valid; further, they have always
been valid.

According to comment 6 there
(https://www.w3.org/Bugs/Public/show_bug.cgi?id=13502#c6), the validator's
behavior is intentional and implements charmod-norm; according to the later
discussion, charmod-norm does not apply to HTML. No change to the visible HTML
spec was needed to fix this (charmod-norm was never referenced in the first
place), but a comment to this effect was added to the document source.

So -- in the first case, where text runs do begin with combining characters,
the validator's behavior is not conforming to the HTML5 spec or any normative
reference.

In the second case, where a combining character follows a zero-width character,
I'd expect a warning not because it violates a spec -- but because it makes no
sense.

Following the resolution of #13502, I changed the referenced web application to
produce text runs that begin with combining characters, and now it gets all
these warnings from the validator. Viewing the source of the page does not show
the relevant characters in red -- they are all in orange (as entity
references); this strengthens the claim that the warning comes from the
validator and not the HTML parser.

Thanks,
Shai.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 21 April 2013 06:37:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:54 UTC