Re: [webcomponents] lang and xml:lang should not use the flat tree (#385)

Can you elaborate how weird it is for you? It looks to me that contents is also weird if it does not inherit. Let's say a page declares `lang="ja"` without specifying `font-family` and my browser picked MSGothic to render all characters including Latin alphabets. Shouldn't English content in the page pick the same consistent font, unless it overrides font or lang? By "environmental" I meant these two attributes can change browsers' default behavior. Components relying on browsers' default need to inherit these two attributes to look consistent. Of course components can pick its own font or lang or dir, in which case they should be honored.

When en/ltr content is inserted as a component into ar/rtl document without declaring lang/dir, they should have ar/rtl. Font fallback and bidi reordering algorithm can take care of such situation. There are some situation where the algorithm cannot determine the correct answer and produce weird results, but that's rather edge cases compared to weird results by not inheriting.

If an application does not honor RTL setting in the OS, it's not usable. If an application honors RTL settings but produces some weird behavior when using on RTL OS, it's a bug. CJK users know poorly localized apps render (c) mark as Katakana on CJK OS, it's a bug, but if it renders all CJK characters as Tofu, it's not usable.

I mean, I agree that there are some cases where not inheriting is better, but I think not inheriting will result in much larger issues. If you have cases that inheriting can cause critical issues such as not-usable, it'd be great to know.

Also, although it's less important than seeking for the right answer, the technical constrain I mentioned earlier is not really ignorable.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/385#issuecomment-185712158