Bug 153794 - Allow setting a manual encoding, and/or encoding autodetection, for WKWebView
Summary: Allow setting a manual encoding, and/or encoding autodetection, for WKWebView
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit2 (show other bugs)
Version: WebKit Nightly Build
Hardware: iPhone / iPad All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-02 11:31 PST by Stuart Morgan
Modified: 2016-02-02 20:35 PST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart Morgan 2016-02-02 11:31:17 PST
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.