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

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 16 Aug 2013 17:23:34 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-12400-169-gpYDsGAOk2@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12400

--- Comment #11 from Michael[tm] Smith <mike@w3.org> ---
(In reply to comment #10)
> (In reply to comment #8)
> > The standards should be realistic about interop.
> 
> Then you should change the standards, overriding the conclusion reached in
> ticket 13502 (and the intentions of UNICODE, as detailed there).

If you want to have a change made to a particular spec, this bug is not the
place to do it.

> To clarify: The problem is that the validator rejects something that the
> standards allow,

The validator doesn't "reject" it -- it emits a warning, not an error. A
warning is appropriate here, given comment 5.

> on the ground that the browsers don't implement it well;

The fact that browsers don't implement it well is the reason the validator is
emitting a warning. The warning is there to let users know that something they
might be think will work correctly actually might not work as they expect.

> effectively undermining the standards committees.
> 
> I find this decision unreasonable.
> 
> (I looked for some guidelines on whether it is OK for me to reopen a bug
> when I disagree with the decision, and couldn't find any; please accept my
> apology if this is a faux pas).

The reason I moved the bug to "resolved" is that in comments here you've
already heard from the maintainers of the validator, neither of whom is
planning to take any action on the bug.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 16 August 2013 17:23:36 UTC

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