[Webkit-unassigned] [Bug 153794] New: Allow setting a manual encoding, and/or encoding autodetection, for WKWebView

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 2 11:31:17 PST 2016


https://bugs.webkit.org/show_bug.cgi?id=153794

            Bug ID: 153794
           Summary: Allow setting a manual encoding, and/or encoding
                    autodetection, for WKWebView
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: iOS
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit2
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: stuartmorgan at chromium.org

There does not appear to be any way to control the encoding used by WKWebView to parse a page. When Chrome for iOS was based on UIWebView, we had an autodetection setting based on network-level interception, but that's no longer possible with WKWebView. We've gotten significant post-switch feedback that there is a long tail of sites, particularly CJK sites, where it's impossible to view them correctly now on iOS.

If WKWebView had a way to override encoding for a page, it would be possible to provide a workaround for the long tail, as is done in desktop browsers.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160202/35332e4c/attachment-0001.html>


More information about the webkit-unassigned mailing list