Closed Bug 1603094 Opened 6 years ago Closed 6 years ago

Distinguish between encoding detector intentionally avoiding UTF-8 vs. other cases in Text Encoding menu telemetry

Categories

(Core :: DOM: HTML Parser, enhancement)

Product:
Core
Component:
DOM: HTML Parser
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1648464

People

(Reporter: hsivonen, Assigned: hsivonen)

References

Details

The new encoding detector added in bug 1551276 deliberately doesn't detect UTF-8 to avoid an adverse feedback loop into Web authoring practices. However, to gauge how much the detector misdetects accidentally, we should distinguish the UTF-8 avoidance case (intentional misdetection) from accidental misdetection when gathering menu usage telemetry.

This involves adding a new value for ENCODING_OVERRIDE_SITUATION histogram, detecting the situation in the parser, and transmitting the information from the parser to the document. I think the best way for the parser to document transmission is to mint a new charset source value.

Rolling this into bug 1648464.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.