Gutenberg too invasive in html blocks (marking them all as invalid)

Hi @locksoft

I’m aware of such an issue and have been tracking it for a while in

https://github.com/WordPress/gutenberg/pull/25120

With WordPress 5.9 I’ve been very busy but I’ll see if I can round up some help to get this fixed once and for all.

It’s a tricky problem to solve but one I recognise needs solving.

Many thanks,

David

Thank you very much, David.

I know that Gutenberg tries to teach us the best way to code in HTML (I understand “his” point of view where an open div could be an issue later in the page), but sometimes I really need to use containers (the example I provided was not the best, but it gives you an idea).
An acceptable solution, I think, it’s to add an option to ignore the code in the block from now on. No need to make it global, as sometimes I really type wrong code and I appreciate Gutenberg efforts to correct it.

At the moment I see that, even if blocks are marked as wrong, the code inside keeps on working, and choosing “convert to HTML” it doesn’t change it (luckly).
But the whole page could be a mess visually. ??

Have a nice day,
Lock

• This reply was modified 2 years, 9 months ago by Lock.

Hi @locksoft

I am aware of several efforts in this area around block validation and HTML.

I’m hopeful you will see an improvement in this area in the (relatively) near future.

I’ll close this one out for now but please do keep an eye on the Issue.

All the best

Ok David, many thanks. ??