Closed Bug 463175 Opened 16 years ago Closed 15 years ago

Categories

(Firefox :: General, defect)

3.0 Branch
x86
Windows Vista
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 61363

People

(Reporter: hans.fast, Unassigned)

References

()

Details

(Keywords: intl)

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506; InfoPath.2; MS-RTC LM 8)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

Uncached pages are loaded twice.
Any page will load twice in FireFox:
<ul>
<li>if the page contains the letter <b>Ä</b> (all "extended" characters triggers this behaviour)
<li>the first time the page loads (the url is not cached yet)
<li>content type is missing from the page
<li>the file is ANSI
</ul>

Reproducible: Always

Steps to Reproduce:
1. Create a simple html page in Notepad
2. Save as file type ANSI (default)
3. Do not include the content type meta tag
4. Write an ä anywhere
5. Put it on IIS (that's what I got, sorry)
6. Load in FireFox 3
7. First time the page loads twice

Actual Results:  
The page loads twice the first time (the url is not chaced?). 

Expected Results:  
Run once.

This might be why the showModalDialog call does not seem to work. Since the page in the modal dialog runs twice it looses the arguments sent to it. And since it only does this for any new url not cached yet, the developer goes crazy ;-)
Severity: normal → major
Keywords: intl
Version: unspecified → 3.0 Branch
Do you have the charset autodetector turned on? See Visa -> Kodning -> Bestäm automatiskt -> Universal.

There is a bug that causes reloads of pages that don't have the meta charset tag in the first 2048 bytes of the file. See bug 61363.
Yes, the autodetector is turned on -> Universal.
About the meta tag, that is a most relevant comment. 
I guess having the meta charset in the first 2048 bytes of the file is a good idea ;-). 
A lot of example pages on mozilla.org don't have that tag, which is kind of ironic. Support for "extended" characters is not build in as the default behaviour. Which it really should be. This is a serious bug causing dataloss and loss of arguments in modal dialogs, etc.
I checked bug 61363, which has been around since 2002 (!) Wow! Guess it might be easier to have the rest of the world stop using "weird" characters in their laguages that fixing the bug ;-)
This bug still exists in 3.0.10
Flags: blocking-firefox3.5?
OK, I'm resolving this as a duplicate then.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Flags: blocking-firefox3.5?
New stuff and workaround added at bug 61363.
You need to log in before you can comment on or make changes to this bug.