Dani Guardiola

@tyxla  Plus style precedence should be handled through [CSS Cascade Layers](https://css-tricks.com/css-cascade-layers/) nowadays, a native CSS feature supported in all browsers for that exact use-case. In the components package, specifically,...

Also, to be clear, replacing emotion with this React API (and something like `precedence="low"`) would instantly improve things today. Emotion actually appends all styles at the end, taking precedence over...

Another relevant note is that there's already some alignment around using layers for other matters within WordPress: https://github.com/WordPress/gutenberg/discussions/61810

> won't that cause compatibility issues with existing plugins and themes that rely on overriding these styles the old way? What do you mean by "the old way"? Unlayered styles...

I will take a look at it

This is awesome, thank you. Please update the README.md (put your name on it as well) and I'll approve your PR right away.

Hmmm, weird... Anyway I have to refactor this a bit so I will update the template when I find some free time. Thanks for the report!

Thanks, though honestly, I feel like this is too complicated. I think the less surprising (for users) and easier to maintain (for devs) path is keeping things very simple and...

Hi there :) any plans to merge this and create a release? Thank you for fixing this!

Hi there! As I said [here](https://github.com/WordPress/gutenberg/pull/62343#issuecomment-2197653070), I think #62343 could be a great base for this change, since it unifies sidebars. I think this is a positive change, and I...