On 20/08/17 00:29, Andy Oram wrote:
I think the situation for each browser may be more complicated than your email
suggests,
I admit I am quite aggravated by this issue. Apologies.
I should have condensed my point to the fact that users *no longer*
can set UTF-8 as the character set to be used if neither the server
or the document itself specifies a character set.
This used to be possible, but is now deliberately disabled.
Perhaps others might take a look at the developer discussion around the
changes, and provide a more balanced summary of the situation?
This functionality was in Firefox until four years ago,
https://bugzilla.mozilla.org/show_bug.cgi?id=815551
https://bugzilla.mozilla.org/show_bug.cgi?id=1071816
https://github.com/mozilla/gecko-dev/commit/5ac2a5be04f63fc1a2ee87f2c4536064072aa71d
and in Chrome until this year:
https://bugs.chromium.org/p/chromium/issues/detail?id=597488
https://goo.gl/47cdcb
Much appreciated,
Nominal Animal
_______________________________________________
libreplanet-discuss mailing list
[email protected]
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
