On 02/08/2010 06:25 PM, Kent Briggs wrote:
> NoOp wrote:
> 
>> Definitely poorly coded in SeaMonkey/Firefox?
> 
> Uh, yeah. 270 seconds of lockup vs 7 seconds. Even that piece of crap IE 
> doesn't do that.
> 
>> <http://validator.w3.org/check?uri=http%3A%2F%2Fwww.whatwg.org%2Fspecs%2Fweb-apps%2Fcurrent-work%2Fcomplete.html&charset=(detect+automatically)&doctype=Inline&group=0>
> 
> Two minor errors in a large document is causing a 270 second load time? 
> I don't think so.
> 

I was thinking that those two issues, being html5 realated (p element)
could be an issue by a client that is checking the code. Perhap IE is
ignoring it...

However, this might be of interest:
http://blog.mozilla.com/standards/category/html5/
<quote>
so Mozilla, along with Opera, started the WHATWG (http://www.whatwg.org/).
</quote>

Using the validator from that article:
<http://validator.nu/?doc=http%3A%2F%2Fwww.whatwg.org%2Fspecs%2Fweb-apps%2Fcurrent-work%2Fcomplete.html>

seems to show OK. So something is definitely wrong; and perhaps you are
right. On the browser click Help|Report Broken Website & report it.
Perhaps the irony of Mozilla and Opera browsers having issues with the
site will lead to a quick resolution?



_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to