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


--- Comment #32 from Addison Phillips <addison@lab126.com> ---
(In reply to Ian 'Hixie' Hickson from comment #28)
> (In reply to Addison Phillips from comment #25)
> > 
> > The page author has no control now. Isn't that an issue?
> Yes. I don't think anyone is arguing that we shouldn't provide authors with
> a way to control this.
> If we want a mechanism to turn localisation on or off, then CSS is probably
> the best place for it, not the markup. In the markup, if we have a
> mechanism, it should just be a way to specify the locale. If we believe
> lang="" is sufficient for that, then there's nothing to add to the markup;
> we only need a mechanism to turn it on, which would be in CSS. If lang=""
> isn't enough, then we can have a new mechanism (e.g. locale=""), and then
> the presence of that mechanism can force the localisation on, and then we
> don't need something in CSS (though we probably still want it, long-term).

I agree with this. I'll note that section has what I consider the
appropriate wording on presentation.

So I guess the way to resolve this bug would be to ask CSS to define a property
that can be set to control (turn on/off) the localization of input elements in
the page?

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

Received on Wednesday, 30 July 2014 15:39:05 UTC