Comment #8 on issue 15801 by js...@chromium.org: US-ASCII encoding can not be displayed on Encoding sub menu http://code.google.com/p/chromium/issues/detail?id=15801
You're right. (sorry I forgot about it). If x-user-defined is specified in HTTP, webkit still honors it. I'm loath to add a new entry to the encoding list especially when the meaning of the entry is ill-defined. Is it really bad not to have x-user-defined entry? Not much, I guess. Nonetheless, if you feel strongly about it, go ahead and make a CL for that along with Chrome-side aliasing of us-ascii to iso-8859-1 and I'll review it. -- 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 -~----------~----~----~----~------~----~------~--~---
