Comment #9 on issue 7243 by [email protected]: Encoding override is not applied to all the "sub frames" http://code.google.com/p/chromium/issues/detail?id=7243
Hi Jungshik, According to analyzing the page you provided, some contents don't change is because those contents are generated by external JS file, and the encoding in the C-T head of the external JS files is "EUC-KR". Now if there is encoding defined in C-T head of external JS resource, WebKit will use it to decode the contents of JS resource. (See CacheScript::set_encoding). To comply with IE's behavior, it looks like we need to give high priority to overrided encoding when decoding the external js resource. But now FF3 is same as Chrome's behavior. So which way does Chrome need to follow? IE or FF? -- 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 -~----------~----~----~----~------~----~------~--~---
