If ViewEncapsulation.ShadowDom is not supported, this should be called out in the docs to save developers time and frustration.
ViewEncapsulation.ShadowDom is not supported and is not documented.
To save developers time and frustration.
Angular: 7.0.0
Angular Material: 7.0.2
TypeScript: ~3.1.1
Browsers: Tested on Chrome, Firefox, and Safari latest stable versions
Nope
Is there any plans to support ShadowDom at some point?
We have to define that "support" means, as well. We'll probably never change the components to _use_ Shadow DOM, but when we switch to CSS variables the theming system won't prevent other people from using it.
@jelbourn where is this on the road map (days, weeks, months)? We're starting to plow headlong into a webcomponent architecture but are heavily invested (and wish to remain so) with our material components.
Are you aware of a way to work around this. Since we're just starting off with componentizing some of our resources, it wouldn't be much effort to make the components happy with angular.
Switching the theming system to use CSS variables is probably going to be early 2020, but for other things (like overlays) we don't have concrete plans yet.
Note that when working with Angular Elements, ViewEncapsulation.None and using Sass (SCSS) to make sure that your styles are scoped to components is recommended at this time.
We are now approaching mid 2020. What is the status and roadmap of this?
Being able to use material in components with ShadowDom opens a lot of opportunities and cleaner components/code/CSS.
Most helpful comment
We are now approaching mid 2020. What is the status and roadmap of this?
Being able to use material in components with ShadowDom opens a lot of opportunities and cleaner components/code/CSS.