[Bug 17859] Mechanism to enable localisation of form controls and other locale-specific data


--- Comment #43 from Cameron Jones <cmhjones@gmail.com> ---
1. The current description of locale was defined through this bug:


2. The problem with making a specific locale a requirement is that there is no
universal default which makes sense for all controls.

3. The best change possible would be to specify which locale should be used for
each control, however this was deemed to be too onerous for HTML and assumes a
particular implementation. 

4. There is already navigator.language so there is no additional fingerprinting
signals exposed by form localization. 

The place to define localization for presentation is not HTML but instead
through CSS. This allows authors to write the content of the page with locale
markup using the "lang" attribute and then configure the style of the page
using the user or element locale through CSS declarations.

This also would provide the mechanism for UAs to define their localizations as
CSS declarations within the default stylesheet.

I broached this on www-style last year but as an esoteric subject there was
little headway at the time. I do note that i18n has interest in resolving this
bug and has produced the following:


You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 6 April 2016 12:47:40 UTC