- From: <bugzilla@jessica.w3.org>
- Date: Sat, 17 Aug 2013 06:55:35 +0000
- To: www-validator-cvs@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12400 --- Comment #12 from Shai Berger <shai@platonix.com> --- (In reply to comment #11) > (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. > It was Henri who suggested there was something wrong with the spec. I would like to see it implemented as it stands. > > 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. > I see. In that case, perhaps the warning message can be made clearer. > > 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. Will you accept a patch to this effect (make it clearer that the warning is about current implementation in browsers)? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 17 August 2013 06:55:36 UTC