Closed Bug 980210 Opened 11 years ago Closed 11 years ago

chrome:// files don't understand windows-1251 despite specified encoding

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Version:
27 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: investfund2007, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release) Build ID: 20140212131424 Steps to reproduce: Hi! I made xul file with <?xml version="1.0" encoding="windows-1251"?> ... <browser src="chrome://myapp/content/test.html"> ... in test.html I have <meta http-equiv="Content-Type" content="text/html; charset=windows-1251" /> and some non english symbols in windows-1251 (they have char code above 128) Actual results: When I start xulrunner I see in place of this symbols "?" Expected results: It should be windows-1251 symbols
Data loaded from chrome:// URIs must always be UTF-8. See bug 617339.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Summary: xul files don't understand windows-1251 despite specified encoding → chrome:// files don't understand windows-1251 despite specified encoding
You need to log in before you can comment on or make changes to this bug.