Fwd: PROPOSAL: require UTF-8 resources to use new web features

Forwarding because this was caught in the moderator queue.

Regards,    Martin.


-------- Forwarded Message --------
Subject: [Moderator Action] PROPOSAL: require UTF-8 resources to use new 
web features
Date: Fri, 26 Jan 2018 23:30:46 +0000
From: Rodger Combs <rodger.combs@gmail.com>
To: www-international@w3.org

This concept recalls Google's push to require HTTPS in order to use 
features that potentially impact user security: 
https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins 
<https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins>

While character encoding selection generally does not have security 
implications, pushing sites towards a common standard is a worthwhile 
goal, and one way to do that without breaking backwards-compabitility is 
to require valid UTF-8 in order to activate newly-introduced features, 
and slowly deprecate support for recent features (that are unlikely to 
be used on abandoned sites) with other character encodings.

Any thoughts?

Received on Monday, 29 January 2018 04:54:58 UTC