Status: Untriaged Owner: [email protected] CC: [email protected], [email protected], [email protected] Labels: Type-Bug Pri-1 OS-All Area-BrowserUI I18N Regression
New issue 8587 by [email protected]: Regression: Encoding auto-detect doesn't work any more http://code.google.com/p/chromium/issues/detail?id=8587 Trunk only issue, OK on latest Dev and Stable channel builds. Build: 2.0.170.0 (Developer Build 11249) OS: Any Other Browsers: Safari4: N/A WebkitNightly: N/A Firefox3.0.7: N/A IE8: N/A Steps: 1. Launch Chrome 2. Make sure encoding auto-detect is enabled 3. Open attached test file 4. Observe Result: With auto-detect enabled, Chinese characters still showing as garbled text Expected: Chinese characters should display correctly Notes: 1. Started from build 11215, OK on build 11201 >>http://build.chromium.org/buildbot/continuous/2009-03-07/ 2. Change log between these two builds >>http://build.chromium.org/buildbot/perf/dashboard/changelog.html? url=/trunk/src&range=11201:11215&mode=html Attachments: gb18030_content_without_encoding_declaration.htm 1009 bytes -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
