- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 13 Feb 2014 13:01:05 -0800
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: www-style list <www-style@w3.org>
On Thu, Feb 13, 2014 at 12:49 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 2/13/14 3:42 PM, Tab Atkins Jr. wrote: >> I think #2 is fairly obviously the "best" answer, but it's hard to >> implement. > > And somewhat nonsensical for font-family, which inherits across component > boundaries (both directions, even)... Yeah, you're right, #2 isn't even obviously "best". It allows for accidental name collisions just as badly, just in a more confusing manner: if the component defines a "foo" font-face which it's intending to use for a particular thing, but the outer page also defines a "foo" face for body text, it'll inherit in and suddenly the component's own "foo", which may not be appropriate for body text, gets used for any text that doesn't override the font-family. So I think just going global is the best answer among multiple bad options. ~TJ
Received on Thursday, 13 February 2014 21:01:52 UTC