Closed Bug 1513517 Opened 6 years ago Closed 5 years ago

Remove UTF-8 as a possible Japanese encoding detection outcome

Categories

(Core :: Internationalization, enhancement, P3)

Product:
Core
Component:
Internationalization
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: hsivonen, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fixed by bug 1543077])

Now that bug 1071816 has landed, the Japanese encoding detector no longer needs to be able to detect UTF-8 for local files. Detecting UTF-8 for http/https resources is bad, because it creates a situation where newly-authored pages (as opposed to deep legacy EUC-JP pages) accidentally end up depending on autodetection, because unlabeled UTF-8 appeared to work in the Web developer's configuration. Considering https://bugs.chromium.org/p/chromium/issues/detail?id=691985 and https://github.com/web-platform-tests/wpt/pull/14455 , we should make our Japanese detector not detect UTF-8.
Marking this as blocking the Encoding Standard under the assumption we'll eventually standardize detection (or forbid it).
Blocks: encoding
Priority: -- → P3

Fixed by bug 1543077.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by bug 1543077]
You need to log in before you can comment on or make changes to this bug.