Al Marks
Al Marks
We should be able to cache the exportsparts tree, maybe directly on each node, so that we don't need to walk the same exporting part ancestor more than once.
Need to ShadyDOM.wrap where appropriate.
See https://github.com/webcomponents/polyfills/pull/329/files#r430699466 The most important reason to do this could be users who don't want to pay the byte cost of additional shadow parts support.
The static parts of a template could be discovered once per template in `prepareTemplateDom`, which could give us a performance improvement. Would still need to account for dynamic DOM insertions,...
Investigate whether/how an optional build step could be used to improve performance of shadow parts support in shady css.
Currently, when an instance consumes a ::part rule that consumes a custom property, and native custom properties are not available, `_applyStyleProperties` ends up getting run twice. Once is the normal...
Document how we will support Shadow Parts in browsers that do support native shadow DOM, but don't support ::part (e.g. Safari).