User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20071127 Firefox/22.214.171.124 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20071127 Firefox/188.8.131.52 The font/language is not recognized in this browser whereas its recognized in IE. Reproducible: Always Steps to Reproduce: 1.Open the link http://eenadu.net/
Doesn't work in Opera 9.25 either, nor Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2008012104 Minefield/3.0b3pre ID:2008012104 And it doesn't use a doctype, and probably has lots of errors in. http://validator.w3.org/check?uri=http%253A%252F%252Feenadu.net%252F&charset=(detect+automatically)&doctype=Inline&group=0 Tech Evang?
It works in Internet Explorer? So we need to think of implementing the same in firefox or mozilla . //Vamsi (In reply to comment #1) > Doesn't work in Opera 9.25 either, nor Mozilla/5.0 (Windows; U; Windows NT 5.1; > en-US; rv:1.9b3pre) Gecko/2008012104 Minefield/3.0b3pre ID:2008012104 > > And it doesn't use a doctype, and probably has lots of errors in. > http://validator.w3.org/check?uri=http%253A%252F%252Feenadu.net%252F&charset=(detect+automatically)&doctype=Inline&group=0 > > Tech Evang? >
> It works in Internet Explorer? So we need to think of implementing the same in > firefox or mozilla . > > //Vamsi No, things don't work like that. If the website doesn't follow the rules, then the website probably won't work in Firefox. It is not Firefox's job to guess how other browsers may handle non-standard html and implement crazy schemes to match them. Having said that, we really need to figure out exactly why Firefox is showing a different result to IE so we can understand who is at fault and triage this bug appropriately.
Firefox chooses windows-1252 as character encoding here using Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9) Gecko/2008061017 Firefox/3.0 None of the auto-detect options are able to find a suitable character encoding. The site suggests windows-1252 and iso-8859-1 as "the correct encoding", multiple times outside the <head> even. Apparently, no information is given in the HTTP headers for this? Imo, in cases such as these Firefox should default to whatever encoding it is able to auto-detect. Not that it would help in this specific case. "content-type" and "GENERATOR" values from page info window text/html; charset=windows-1252 text/html; charset=windows-1252 text/html; charset=iso-8859-1 Mozilla/4.8 [en] (WinNT; U) [Netscape] text/html; charset=iso-8859-1 Mozilla/4.79 [en] (Windows NT 5.0; U) [Netscape] text/html; charset=iso-8859-1 Mozilla/4.8 [en] (Win98; U) [Netscape] Header information according to Bugzilla Response Headers Date Sat, 05 Jul 2008 00:28:26 GMT Server Microsoft-IIS/6.0 X-Powered-By ASP.NET Content-Length 103242 Content-Type text/html Cache-Control private Request Headers Host eenadu.net User-Agent Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9) Gecko/2008061017 Firefox/3.0 Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language en-us,en;q=0.5 Accept-Encoding gzip,deflate Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive 300 Connection keep-alive Cookie eenadu=eenadu; ASPSESSIONIDQQTCSSBS=LMPKDEOCKMENPOGPPAJFCFPF Cache-Control max-age=0
This bug was originally reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.6 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.