- From: Ryosuke Niwa <rniwa@apple.com>
- Date: Wed, 11 Nov 2015 07:47:47 -0800
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: www-style@w3.org
> On Nov 11, 2015, at 7:23 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > > On 11/11/15 3:51 AM, Ryosuke Niwa wrote: >> Oh, I see. I was conceptualizing that we only store data on parent elements as that's how WebKit's styling system works but storing font face data on text nodes work as well. > > OK, so the important part here is that there is a separate font face set attached to every "node scope", right? > > Have you examined the performance characteristics of this? Font face sets do a bunch of caching, and it sounds like it will all need to be redone on a per-shadow-tree basis, so somewhere between "a few" and "hundreds" of times per page, no? Our thinking is that, components either don't include @font-face rules, or use the same set of rules in multiple shadow trees (e.g. multiple instances of the same custom elements) such that implementations can share the cache between multiple shadow trees. - R. Niwa
Received on Wednesday, 11 November 2015 15:48:18 UTC