Global block defaults shouldn't be applied directly to individual blocks

[rchipka]

Many of the global defaults options are just CSS settings, like the Padding/Margin settings for Row Layouts.

It appears that, by setting a default for one of these values, the global default (at that time) will be saved directly onto the block itself.

This is an issue because, should you want to update the defaults for a site, you can only do so going forward.

There's no way to retroactively update existing blocks, even if they're taking on a default.

Ideally these defaults would be recorded by reference instead, or at least be injected into a shared global stylesheet or <style> tag where applicable.

This way global defaults can be modified in bulk should a site's design or theme change.

Any deviation from the default would then be seen as a specific override that should be retained even if the defaults change.

[kadencewp]

Hey, This isn't the current purpose of block defaults. Although I do like what you are suggesting, and global styles are a thing that might become an option at some point in time. Page builders like brizy do this well. Allowing you to link items to the global styles or keep them separate. I imagine if I create something like that it would work similarly.

Or block defaults are not meant to work like that instead they are meant to allow users to predefine what they want to use the blocks for and how they want the settings to be at the initial stage. This allows you to speed up development. The plan is to have exportable and importable defaults really soon.

It's worth noting that while many settings have to do with css, many don't and it would be impossible to make those types of block settings "global styles" since the markup changes quite a bit based on the settings.

Ben