W3C home > Mailing lists > Public > www-validator@w3.org > December 2010

Re: Possible bad html passing validator

From: Paul Allen Newell <pnewell@cs.cmu.edu>
Date: Wed, 08 Dec 2010 23:29:15 -0800
Message-ID: <4D00854B.60805@cs.cmu.edu>
To: Tatham Oddie <tatham@oddie.com.au>
CC: "peasthope@shaw.ca" <peasthope@shaw.ca>, "www-validator@w3.org" <www-validator@w3.org>, pnewell@cs.cmu.edu
On 12/8/2010 11:15 PM, Tatham Oddie wrote:
> Hi Paul,
> 	>  At least I feel like I stand a better chance of a reply than
> asking Microsoft (smile).
> There are well establish avenues for submitting bugs to Microsoft.
> If you ever have any issues, or want help navigating them, feel free to ping
> me personally and I'll help you through.
> --
> Tatham Oddie
> au mob: +61 414 275 989, us cell: +1 213 280 9140, skype: tathamoddie
> If you're printing this email, you're doing it wrong. This is a computer,
> not a typewriter.
> -----Original Message-----
> From: www-validator-request@w3.org [mailto:www-validator-request@w3.org] On
> Behalf Of Paul Allen Newell
> Sent: Thursday, 9 December 2010 1:05 PM
> To: peasthope@shaw.ca
> Cc: www-validator@w3.org; pnewell@cs.cmu.edu
> Subject: Re: Possible bad html passing validator
> On 12/8/2010 8:34 AM, peasthope@shaw.ca wrote:
>> Paul,
>>> ... W3C Markup validator ...
>> Yes, your code validates.  The warning will not be issued if the
>> document comes from a Web server which specifies UTF-8.
>>> I have a document that is giving faulty display on my Win XP SP3.
>> Iceweasel in Debian Linux displays the document correctly.  The
>> problem must be in your browser.  Perhaps another Windows user has a
>> work-around; or ask Microsoft.  [Flippancy; sorry.]
>> Regards,                ... Peter E.
> Peter:
> Thanks for reply. Courtesy of Philip Taylor's suggestion, I ran a browser
> test and it works in IEbut not Firefox. So, I am now trying to figure out
> best avenue to send as a potential bug to Firefox. At least I feel like I
> stand a better chance of a reply than asking Microsoft (smile).
> Paul

Thanks for the offer of help. The feedback I am getting from Firefox 
folks via Bugzilla is that it can't be reproduced and I am probably 
looking at my machine being corrupt. I've already verified on my Linux 
boxes that I can't see the problem, including the same Firefox 3.6.12.

Not happy about this prospect, but grateful for all the help in drilling 
down far enough to point the finger at my machine. To be honest, it 
makes sense as this issue is something that others would have already 

Received on Thursday, 9 December 2010 07:29:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 14:18:02 UTC