On 8/19/10 3:31 PM, Lance Courtland wrote: > Win XP SP3, SM 2.0.6 > > When I go to http://www.alternet.org, SM crashes every time. It didn't > used to a few days ago. I have tried with and without Adblock plus > 1.2.1. Makes no difference. > > When I use Prefbar 5.1.1 and change the User Agent to "IE", > > js:useragent="Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)"; > appname="Microsoft Internet Explorer"; appversion="4.0 (compatible; MSIE > 6.0; Windows NT 5.1)"; platform="Win32"; > > or "IE UA" > > Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.2; Trident/4.0; SLCC2; > .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center > PC 6.0) > > everything works OK. > > When I run the URL through the HTML URL Validator, > > http://validator.w3.org/check?uri=http%3A%2F%2Fwww.alternet.org%2F&charset=(detect+automatically)&doctype=Inline&group=0&verbose=1&user-agent=W3C_Validator%2F1.1 > > it says "Sorry this document can not be checked", and gives an error > message; > >> Sorry, I am unable to validate this document because on line 223 it >> contained one or more bytes that I cannot interpret as utf-8 (in >> other words, the bytes found are not valid values in the specified >> Character Encoding). Please check both the content of the file and >> the character encoding indication. >> >> The error was: utf8 "\xC8" does not map to Unicode > > Does anybody else get the same results? > Is this bad sniffing combined with a coding error? > > TIA > > Lance
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6 Extensions (enabled: 6) * Adblock Plus 1.2.1 * DOM Inspector 2.0.4 (http://www.mozilla.org/projects/inspector/) * Flashblock 1.3.16 (http://flashblock.mozdev.org/) * Live HTTP headers 0.16 * PrefBar 5.1.1 (http://prefbar.mozdev.org/) * Show Password On Input 0.1.3 (https://addons.mozilla.org/thunderbird/addon/6143/) * ShowIP 0.8.19 (http://code.google.com/p/firefox-showip/) I have no problem viewing the page without any spoofing. The page validates with 156 errors if I force the W3C validator to use iso-8859-1 character encoding. However, the <head> section explicitly states UTF-8 encoding. There are also 78 CSS errors. The problem is that, at line 223, the bytes x(c8) appear. This is an upper-case E with a grave accent and is not allowed as such in XHTML with UTF-8 encoding. Overall, this page is garbage. I'm surprised that I was able to view it. -- David E. Ross <http://www.rossde.com/> I filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of the amount of spam from that source. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
