[Webkit-unassigned] [Bug 17873] Encoding override should not be persistent

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Mar 17 10:49:43 PDT 2008


http://bugs.webkit.org/show_bug.cgi?id=17873


jungshik.shin at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jungshik.shin at gmail.com




------- Comment #7 from jungshik.shin at gmail.com  2008-03-17 10:49 PDT -------
(In reply to comment #2)
> Something we should not regress is navigating within a site that reports an
> incorrect encoding in its HTTP headers. 

Is there a reliable way to determine that new pages loaded are in the same site
and they have the same problem as the page for which a user overrides the
encoding?  
I guess the former is possible, but I'm afraid it's hard to determine the
latter. 

If what I'm writing is the case, I guess it's better to be simple (to
understand/explain) and predictable and to do what other browsers do. 

After all, those misconfigured sites need to correct themselves. And if they
went extra length to convert their pages to  MacCyrillic (on the fly) ,  
wouldn't they listen to a request for either  not doing it (just use the
encoding they use for Windows) or using the correct charset name? 


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list