@Louis Just following up on this, as it is a client facing issue and affects the client’s editing experience it will be good to solve this when possible. Thanks.
I use a dedicated class on post content blocks, like .editor-wrapper-style, so that I can have more freedom on this.
Indeed, on frontend, my content blocks may have some padding or not, depending on templates, different width, background, etc. And I don’t want to systematically apply everything on backend.
This is especially important with padding, since most of the time my post content is nested inside a bigger wrapper (main or section) with padding, so my post content doesn’t have padding, but on the contrary I need it in the editor to prevent content from reaching the edges.
We were doing something similar before this setting was introduced and have had to put it back in place in the meantime, it is just unfortunate because with different sites being on different versions, as soon as you upgrade, you have to keep track of which site has the workaround and which doesn’t. We were hoping this would be fixed, so we wouldn’t have to add the workaround to the other sites.
I think perhaps I will go with custom code approach to save time.
@Louis, We have many sites, some with tailwind, some without, of the two that I have recently tested and replicated this on, both have mobile first breakpoints (as per Tailwind reset), one is actively using Tailwind, the other is not.
