Hello, This is not really a bug, but rather a question about the design decision. When you are using a component, let’s say s-badge, properties are reflected in the underlying shadow dom. For instance, the tone attribute is added as a class: [image] The code is minified so it’s hard to see, but…

Some early component prototypes had this type of selector, but we ultimately chose not to do it because ultimately we decided that attributes are for configuration and that It also makes sense that validation applies when getting/setting properties, but never when getting/setting attributes. So …

Hey @bakura10 the main reason we didn’t put styles on the :host is that we no longer control them. With the components being shipped to a CDN and our need to ship updates confidently without breaking applications it means that we cannot without extreme added risk move styles to that selector. With …

That’s incorrect @alex-page . I was not referring about setting the style on the component itself. But just use the host to avoid having to reflect the properties and use attributesChangedCallback to re-render the component. For instance instead of: .badge { background: grey; } .badge.tone-warn…

Using class vs host

Polaris

bakura10 July 3, 2025, 12:54am 6

Hi @Anthony_Frehner ,

Those are great points and seem all valid to me, thanks for clarifying!

Considering using Tailwind?

Topic		Replies	Views
Considering using Tailwind? Polaris	0	108	July 15, 2025
How does it interact with Polaris React? Polaris	10	1104	December 5, 2025
Polaris tokens - where to get new versions? Polaris	7	303	September 18, 2026
A recent change in Polaris broke some part of our app Polaris	8	222	July 6, 2026
Polaris Link Web Component and slot attribute inside Page Polaris	3	136	February 3, 2026

Using class vs host

Related topics