W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > July 2008

Re: [Fwd: Questions on Checker]

From: Francois Daoust <fd@w3.org>
Date: Thu, 10 Jul 2008 09:17:51 +0200
Message-ID: <4875B79F.5010603@w3.org>
To: Sean Owen <srowen@google.com>
CC: Jo Rabin <jrabin@mtld.mobi>, public-mobileok-checker <public-mobileok-checker@w3.org>

Sean Owen wrote:
> (Is the document returned to a desktop browser the same as what is
> returned to the checker? maybe so, but I have not checked this.)
> I wonder, do we check for "UTF-8" in a case-insensitive way? well
> there's a bug if we don't.

We are, AFAICT. I see checks with "equalsIgnoreCase" all over the place...

> The error is on a style with selector ".hr" which isn't used in the
> main doc. Is that still an error?  yeah I think so. If it's not used,
> it shouldn't really appear anyway in the response to a mobile request.
> I don't think it's necessary to get into deciding whether the rule is
> used. It's still valid to flag this one.

I think so as well.

> On Wed, Jul 9, 2008 at 5:21 PM, Jo Rabin <jrabin@mtld.mobi> wrote:
>> I just ran
>> http://validator.w3.org/mobile/?docAddr=http%3A%2F%2Fwapreview.mobi%2F
>> and was surprised to see the character encoding error. Looks to me like the
>> xml declaration does specify utf-8.

The checker that is at http://validator.w3.org/mobile is still the beta 
version. There's one bug in there about redirections that was fixed not 
so long ago.

... returns a 302. The HTML body response of this 302 triggers the error 
(Apache typically sends 302 responses encoded in ISO-8859-1 IIRC, and 
there's no easy way to change that behavior). But the checker should not 
check the response.

Typically, the error is not returned when checking:

Dom fixed the bug in the library.
I'll update the checker used http://validator.w3.org/mobile when we get 
a v0.99999 version. Hopefully today.

Received on Thursday, 10 July 2008 07:18:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:20 UTC