- From: L. David Baron <dbaron@dbaron.org>
- Date: Wed, 18 Sep 2013 08:10:01 -0700
- To: Elliott Sprehn <esprehn@chromium.org>
- Cc: Peter Occil <poccil14@gmail.com>, WHATWG <whatwg@whatwg.org>
On Wednesday 2013-05-01 01:01 -0700, Elliott Sprehn wrote: > On Wed, Apr 24, 2013 at 9:22 AM, Peter Occil <poccil14@gmail.com> wrote: > > I have no objection to the name "baseLang" rather than "language" as the > > name of the DOM attribute. > > > > But if there isn't more interest or you decide not to add this DOM > > attribute, I encourage you to at least: > > > > > fwiw WebKit (and Blink) implement this through CSS inheritance since you > need to know the lang for all kinds of things and walking up the DOM > repeatedly would be expensive. > > -webkit-locale is inherited by default and contains the enclosing @lang > value. You can query it through getComputedStyle(node).webkitLocale. That > doesn't help your custom parser though. In Gecko it's also implemented through CSS inheritance, but it's not exposed to Web content as a CSS property. (Internally it's '-x-lang', but that name isn't exposed.) We use the language for: * font selection * language-specific text-transform behavior * hyphenation (which doesn't work unless it's explicitly specified, as required by http://dev.w3.org/csswg/css-text/#hyphens-property ) -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
Received on Wednesday, 18 September 2013 15:10:32 UTC