Daniel Richards

cc @jasmussen @richtabor Seems like users are having issues inserting blocks at the bottom of the post editor after https://github.com/WordPress/gutenberg/pull/60697. There were also a few comments in #63882.

It looks like there was a recent regression with the click below to add a block after #64639 in the iframed editor. The PR #64992 fixes it in my testing,...

> @talldan retesting this PR after the latest commits shows a regression. The global styles data isn't accessible to the non-admin user anymore and the block style variation styles aren't...

I think it'd be good to bring some REST API folk into this conversation (maybe @TimothyBJacobs?). Also some other contributors that know global styles well (perhaps @oandregal and @ajlende?). (The...

> There's probably some work to be done on the REST API, to be able to fetch the patterns using the same REST API regardless of where they come from....

> Should the issue be updated to reflect the plans for WordPress 6.8? Feel free to, this was only ever a draft, and never really got past that stage. It...

I'm going to close this - I originally penned the issue as a draft for 6.7, which was a while ago now. We can make a new issue if there's...

@chrisandrew-dev Thanks for reaching out. The hashed classnames are now used to support some of the newer advanced uses of block style variations that have theme.json declarations. They can support...

Yep, I can also repro, I'll see if I can fix it.

> Let's make current contentOnly less restrictive by: > Allow hitting ENTER to add a block (e.g; paragraph, list block...etc). > Add ability to delete content blocks (not the top...