Aaron Robertshaw

> the specificity of block style variation selectors needs to be 0-0-0. This was incorrect. Block style variations only need "level" specificity so they match the specificity of global block...

I've updated this PR to be based on top of the [work being done](https://github.com/WordPress/gutenberg/pull/46579) to bundle `WP_Theme_JSON` instead of inheriting per WordPress version. I'll be AFK for a couple of...

I really appreciate the feedback @gziolo, it's great to have you back online! > It's going to be a bit more work inside WordPress core. All top-level block-type properties need...

Some draft documentation has been added via https://github.com/WordPress/gutenberg/pull/46496/commits/ce4754d9e2cfdbf7d37f1e65d042ba6476f4db65 to get the discussion started. I'm out of time today but will come back and refine it into something more readable tomorrow.

Thanks for taking the time to review this @gziolo 🙇 I believe I've addressed all the current feedback here and on the core patch. I ultimately decided to make the...

> I know this feedback is coming very late, and I am probably missing important context, but what do you think about the selector living within the supports key, as...

> Would it be a good idea to support a separate editor-only selector in the stabilized API? Thanks for raising this @ajlende 👍 I'd definitely like to see something like...

> I have one question about the whole selector feature 🤔 Thanks for the question @fabiankaegy 👍 > Are there any plans to also make this work for dynamic blocks?...

@ajlende I've updated this PR to include support for editor-only selectors and the revised location for duotone (`filters.duotone`) if you'd like to take it for a spin. The related [core...

Thanks for testing @ajlende 👍 > Global styles image border seems to be working fine on the frontend, but it isn't showing up in the editor. Global styles for the...