Ben Dwyer
Ben Dwyer
@andrewserong I see, it's more complicated than I realised. I've pushed up a different and simpler approach, which seems to work. In essence, we always output the core theme.json defaults...
@andrewserong Thank you that seems to solve it. I've tested both classic and block themes and neither have duplicate styles, but the buttons look correct in both.
I wrapped the button selectors in a `:where` which makes them less specific. I've tested classic and block themes in both the frontend and the editor. The search block looks...
Another option is to keep these rules but also add the CSS back to the block...
I think this approach is always going to need some intervention from some themes. I tried a different approach in https://github.com/WordPress/gutenberg/pull/44334.
> I don't know enough about why the button styles were moved to the default theme.json. Need to go deep into this more. Ideally, we'd be able to have these...
> My thinking is that we should always load the theme.json of the blocks for any theme, in the same way we ship presets and variables. This would solve the...
I think if we want a truly clean slate we should remove a lot more - all the patterns for example can go, and quite a few of the templates...
What happens if we remove all templates except index?
I'm not clear how "blank" we want this to be. The templates still contain a lot of opinion. Do we want to strip it back to just display page content?