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

[bugzilla-daemon at webkit.org]

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

            Bug ID: 245305
           Summary: Implement general encoding sniffing
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Media
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: gsnedders at apple.com
                CC: ap at webkit.org, bfulgham at webkit.org,
                    webkit-bug-importer at group.apple.com

Every other major browser engine has some form of encoding sniffing, and has for years. We have, consistently, resisted having much, preferring to be more conservative with any sort of magic heuristics. (Currently, we do a small amount of sniffing if the OS language is Japanese between different Japanese legacy encodings.)

To quote:

(In reply to Alexey Proskuryakov from comment #3 to bug 78584)
> > However, it should not prevent to run auto detector, if users enable auto detector.
> 
> This is something I'll take issue with. Proliferation of encoding detection
> in one browser essentially randomizes what users and authors see. It's
> barely acceptable to sniff when there is no encoding indication at all, but
> not when there is an established behavior already.
> 
> More encoding detection is bad for the Open Web, not good.

Henri Sivonen has previously written about this at https://hsivonen.fi/chardetng/, with regards to Firefox's modern character detection, and I know he had some interest in standardising this if anyone else was interested in implementing.

rdar://17033341

-- 
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/20220916/02e6dc20/attachment-0001.htm>