Primary eng (and PM) emails
Link to “Intent to Deprecate” thread
https://groups.google.com/a/chromium.org/d/msg/blink-dev/1bykHAUpEA0/1Rl1AZuaiS4J
The deprecation landed in M41:
https://codereview.chromium.org/768313004
Summary
Make Document.charset readonly. Currently, the setter influences the encoding used for form submissions and the fallback encoding for external scripts and stylesheets loaded after that point.
Motivation
Document.characterSet is the standard attribute, but everyone except Gecko also supports charset, which unlike characterSet can be set.
Document.charset (getter and setter) has ~3.5% usage so I filed a bug to standardize it instead of spending time trying to remove it:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27436
Anne's last comment is "I want to wait with adding .charset until at least the setter has disappeared. Removing that seems like a win for everyone. Then we can evaluate again."
Usage information from UseCounter
https://www.chromestatus.com/metrics/feature/timeline/popularity/427
Usage hasn't changed much since deprecation it's still ~0.01%.
Entry on chromestatus.com
None, just https://crbug.com/438392
Compatibility Risk
Forms may be posted and scripts/stylesheets loaded with the wrong encoding. (They would in Firefox as well, unless it's a non-Gecko code path.)
Judging by a quick grep of the 20150101 httparchive data, the most common way this is used is to set an encoding immediately before form submission. Some are conditional on IE sniffing and based on a Stack Overflow question I suspect that working around an old IE bug explains some of the usage. For per-form control over encoding, the accept-charset attribute is a suitable replacement.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
For per-form control over encoding, the accept-charset attribute is a suitable replacement.