Daniel Richards

> It's seems sensible apart from the duplicate aria-label See https://github.com/WordPress/gutenberg/pull/44291#pullrequestreview-1114900547 for some context. TLDR, it may be best to keep the duplication. It could be worth adding a comment...

We tested this during the core editor triage (https://wordpress.slack.com/archives/C02QB2JS7/p1564035774193100 - slack link, requires signup to slack). I was able to reproduce the issue. My hunch is that it might be...

This works well, the only thing I've noticed that would be nice to fix is that the error doesn't clear when the css field is empty: ![Screen Shot 2023-01-31 at...

I created an issue for discussing the preloading of site editor content over here: https://github.com/WordPress/gutenberg/issues/35942 That would get rid of the disorienting nature of loading the editor. It might not...

It seems like the post editor also needs some work now, possibly since the iframe was introduced: https://user-images.githubusercontent.com/677833/216228500-6cb53e6f-96c1-4d3d-b186-e966d49b1d87.mp4 It might be a different problem though, it's more likely that the...

I've made an issue for it - https://github.com/WordPress/gutenberg/issues/47724.

> I think what @talldan said in the referenced issue is that for standard List View it's ok because clicking on the node causes the block to be selected. That's...

> The only thing is that they don't. If we had it like List View then when you click on any node it would immediately select that block and thus...

It is a bigger button, yes. My preference is still to simplify the code, and all I'm doing is stating that, and pointing out they both do the same thing...

@draganescu It seems like we're going over the same conversation repeatedly. We're allowed to have different opinions. I'm not blocking anything and suggested two potential code solutions that you're free...