[Webkit-unassigned] [Bug 245305] Implement general encoding sniffing

[bugzilla-daemon at webkit.org]

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

--- Comment #6 from Karl Dubost <karlcow at apple.com> ---
There are probably a couple of things that could be taken into consideration.

* The Web from today is massively better than 10 years ago for the encoding story. Many more people are working with UTF-8. The toolchain, the server, the OSes have been converted to using UTF-8 by default. Win for the open web.

* The legacy (not as irrelevant but unmaintained) Web will not be updated and will stay encoded with weird mistakes, hacks, etc. The person using such a site here suffers when the page is broken and not readable. That's the theme of webcompat where we try to fix things for the users. 

* The probability of having reports about wrong encoding probably gradually goes down with time.  It's hard to know if the bugs are reported at all and it also depends on the market. As Sam mentioned, Japan which has a huge iPhone market share, needs some forms of encoding detection so the sites are not broken on these devices. Safari on iOS doesn't have a menu item to report bugs, that probably doesn't help either. Safari on macOS has "Send Safari feedback".

I do not have a strong feeling either way. It would be good if it could be actually measured to understand the extent of the issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220922/dbc3eca1/attachment.htm>