Bug 153794
| Summary: | Allow setting a manual encoding, and/or encoding autodetection, for WKWebView | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Stuart Morgan <stuartmorgan> |
| Component: | WebKit2 | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | andersca, ap, eugenebut, sam, webkit |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | iPhone / iPad | ||
| OS: | All | ||
Stuart Morgan
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |