419594 - IE does not show pictures in files with Cyrilliс name saved in Firefox

Status: RESOLVED WONTFIX

(Firefox :: File Handling, defect)

Description

[Timur Timirkhanov]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008022404 Minefield/3.0b4pre

This is a regression from bug #409796 which was fixed on 24 February, 2008.

Reproducible: Always

Steps to Reproduce:
1. Save a webpage in a file with cyrillic filename.
2. Open the webpage in IE (I used 6.0 shipped with Windows XP SP2).
3. Open the webpage in Firefox 2 or trunk (I used Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008022404 Minefield/3.0b4pre and Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12). 

Actual Results:  
No pictures are shown or styles are applied in IE, but they do in Firefox 2 and 3.

Expected Results:  
Pictures shown and styles applied in both IE and Firefox.

Comment 1

[Timur Timirkhanov]

Adding dependency

Comment 2

[Evgeniy Ivanov]

I have an idea how to fix it.
As I understand http://www.w3.org/TR/html401/charset.html
Everything in the .html should be encoded in the charset specified in the meta tag, am I right?
For example, if we have charset=win-1251, should all the text in the .html be encoded in win-1251 (including attributes of the src=). And escaped links? At this moment we write directory name in escaped utf8.
If we change utf8 to any charset we have to change the open routines (becouse by default it uses path in utf8). If we have win-1251 string in src="" it will be concatenated with full path in utf8.

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

current firefox always encodes file URIs in UTF-8. anything else is lossy.


So I see two options, WONTFIX this bug or generate ASCII names for the files we save

Comment 4

[Evgeniy Ivanov]

(In reply to comment #3)
> current firefox always encodes file URIs in UTF-8. anything else is lossy.
Is it just internal representation of URIs? I guess yes, because there are a lot of non-UTF-8 pages with Cyrillic links. When we open the page we may convert the links from the charset specified in the meta to UTF-8, and when write - from UTF-8 to the page's charset.

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

I was only referring to file: URIs. For HTTP we do this differently.

Comment 6

[Evgeniy Ivanov]

The link from biezi: https://bugzilla.mozilla.org/show_bug.cgi?id=278161
Converting the names to ASCII may be a bad idea for webdevelopers (but good for users). If links are converted some people will have problems. It's more convenient to force everybody to use FF instead of IE and Opera.

Comment 7

[Timur Timirkhanov]

I doin't think it is possible to make 70% of people use Firefox, since most of them don't know what it is.

Comment 8

[Evgeniy Ivanov]

I've tested ff b3 (without patch from 409796) and got the same. Since it isn't a regression I have changed the description of this bug. Also I'm not able to play with it right now, so reassign to nobody.

Comment 9

[Christian :Biesinger (don't email me, ping me on IRC)]

(In reply to comment #7)
> I doin't think it is possible to make 70% of people use Firefox, since most of
> them don't know what it is.

But to see the bug you need to save the page with Firefox first...

Comment 10

[Evgeniy Ivanov]

Numeric character references may solve the problem with utf-8 pages. But I don't think it may solve the problem with cp-1251 and another pages encoded in non-UTF-8. Tests are required. As proxyvictim told testcases are required too.

Comment 11

[Christian :Biesinger (don't email me, ping me on IRC)]

why wouldn't they solve the problem with non-utf8 pages?

Comment 12

[Timur Timirkhanov]

As the author of this bug, I'd like to confess initial addition of regression keyword as a mistake of mine. In fact, this is not a regression from bug #409796.
This exsisted long before the latter was fixed.

Comment 13

[Evgeniy Ivanov]

(In reply to comment #11)
> why wouldn't they solve the problem with non-utf8 pages?

As I saw IE uses page settings to encode links. And also I have found that ff can't open win-1251 pages saved with IE.
I will create some testcases (attach html files and diffs) a bit later (maybe tomorrow).
 

Comment 14

[ru-vadik]

Firefox 3 himself does not show pictures in files with Cyrilliс name saved in Firefox

My UA is "Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9) Gecko/2008052906 Firefox/3.0"

URL is "http://forum.mozilla-russia.org/viewtopic.php?id=24037"

Saving name is "Кириллица" ("Cyrilliс" in Russian)

Comment 15

[Timur Timirkhanov]

ru-vadik,

This bug is not about Firefox 3, it is about IE.
Second, what program did you save your Кириллица.html with?
Anyway, Firefox 3 does show all the pictures.

Comment 16

[ru-vadik]

Timur Timirkhanov,

I'm saved page with Firefox 3

Я сохранил страничку в Firefox 3 и им же потом открыл ее. Пути к рисункам и стилям оказались искаженными и Firefox 3 их не загрузил.

Comment 17

[aleks]

Please
Do it so as K-Meleon  or  give parameter saved in options
because latinian name of file  is chinese fo me and i whont have posible open saved file with IE on anothe computer
Иф ит диффикулт рид фо ю (If it difficult read for you), may be you undestend whith problem

Comment 18

[Jonathan Watt [:jwatt]]

Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)

Comment 19

[Timea Cernea [:tbabos][inactive]]

Hi Timur,
This issue is a really old poke but could you give us an update here? Is this still reproducible or relevant in the latest Firefox version?

Comment 20

[Timur Timirkhanov]

Hi, Timea,

I can confirm this bug is reproducible using Firefox 93.0 and Internet Explorer 11.0.
My opinion is that this bug should be WONTFIX'ed because MS has announced it will stop supporting IE in 2022 except for in Win10 LTSC.

Comment 21

[Timea Cernea [:tbabos][inactive]]

I see, thanks for the update! I will close this issue with wontfix, as you also suggested. Thanks again!