Did'nt mean the css parser, but the parse+DOM operations involved in `.innerHTML` parsing and creating a <style> element for each instance.
There is overhead for the SD, but the difference is often made up for by the faster scoped style resolver: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/css/resolver/ScopedStyleResolver.h?sq=package:chromium&dr=CSs …
-
-
What SD gives you that you can't get any other way is style resolution that operates over the rules you actually need to consider.
-
At scale, this helps you go faster in 2 ways: 1.) fewer global rules to consider in light-DOM style resolution 2.) scoped resolution faster
- 1 more reply
New conversation -
-
-
In theory what overhead does the non-shadow impl have to incur that the shadow impl does not, assuming they both have to use `all: initial`?
-
As I mentioned, global resolution difference. SD operates on less style per element, scales *much* better.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.