Bernie Reiter

> In most cases I expect the resolution would be to remove the block, which is already possible within the list view UI. I suppose we'd need to figure out...

Thanks James for this latest iteration -- looks good to me! > Such examples also make me wonder whether there should be a severity factor applied to the errors. These...

> I recommend removing that code as proposed in this PR and fixing the cause that deemed the code necessary. I wouldn't presently merge this PR as it would cause...

@SantosGuillamot Thank you for your investigation! @sybrew It seems like we aren't able to find any discernible differences of how `cpage` is set by Block Themes vs Classic Themes. Could...

@darerodz and I dug a bit deeper into this issue today. With the TSF plugin installed and active, it was quite easy to reproduce that there's a difference between Classic...

> With FSE, all the page's blocks, including the comment blocks, are parsed right before action `wp_head` (after `wp`). Because of this, when it's time to render the page, the...

How does this relate to `create_fragment`'s `$context` argument? The latter is currently [hard-wired to ``](https://github.com/WordPress/wordpress-develop/blob/f9418c7c3df66a46df00354f93cee92e73601bd3/src/wp-includes/html-api/class-wp-html-processor.php#L296-L298). It seems like `create_fragment_at_current_node` will allow to bypass this limitation (as it sets the new...

Committed to Core in https://core.trac.wordpress.org/changeset/59444/.

Closing in favor of #7443.

> I'm assuming we're going to need to open a GB counterpart to deal with the same logic for adding variation class names in the editor too? Oh, good point!...