293605 - Wrong encoding after page reload

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Ignas Urbonas]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Shows page in wring encoding every 2'nd time after page reload (Reload button).
Page Encoding is UTF8 - page info shows that. But Forefox detects that as
"ISO-8859-5" - russian.
This problem occure some other pages (Not UTF) sometimes - not every time. 
In page info firefox shows different encoding.

Reproducible: Always

Steps to Reproduce:
1.Open page http://www.eniro.lt/imones/rubrika/C110
2.Press Reload button.



Actual Results:  
Russian letters (kirilica) instead lithuanian (UTF8).

Expected Results:  
Lithuanian letters.

Comment 1

[Ben Fowler]

This could be one of the 'Incorrect charset detection bugs' Your server
is not sending back a charset in the http Content-Type header, so
Firefox should be entitled to decide for itself, if necessary by
sniffing. (I may be off-topic for this report, but I believe that it can
be correct for a server to send no charset if it does not know the
correct character encoding

Since the page has a <meta> tag giving the charset (as I see it,
correctly) as utf-8, I don't see why this process should ever give
errors; though I am not claiming that it is always going to be 100%
robust.

It is possible that you need to have the correct setting in your Auto
Detect Menu (View->Character Encoding->Auto-Detect), but I am not sure
that an error here could cause what you seeing.

FWIW, this is WFM; but for ought I know there could be some factor in my
browsing set-up that hides the problem.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.