Implement Shadow DOM support for mixins. Similar to how we have a separate pass to extract mixins from a TreeScope before creating the RuleSets, we now have a separate pass to extract mixins from _all_ relevant TreeScopes before creating any RuleSets. This allows us to implement mixin inheritance, where we pull in mixins from parent TreeScopes to the set of effective mixins, allowing a stylesheet in Shadow DOM to use a mixin from its parent. We still do not support invalidation of mixins, so if you modify a mixin in a parent TreeScope, we will not mark any child (shadow) TreeScope as dirty, and the RuleSets will not be properly updated. Change-Id: I940dbd982724cad6821013745ca1897d31311ae7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6828630 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Steinar H Gunderson <sesse@chromium.org> Cr-Commit-Position: refs/heads/main@{#1500720}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.