Compiling a list of bugs, shortcomings, and enhancement ideas I run into when preparing for the go / no go demo.

• Switch the Page List block to client-side rendering #35632

There's a lot of small issues related to the roundtrip a ServerRender block needs to do for any change and a great showcase for why they should be avoided entirely for any interactive block.

• Pressing shift + click within a rich-text block nested inside a group would lock you out of editing. This one is pretty frustrating.([Block Editor]: Fix selection by holding shift key for nested blocks #35668)

• Navigation block new link would break with no visible signs of recovery — typing the name of the page would not bring the page up.

Generally can happen after leaving the page open for a little bit or interacting for a while. It's understandable connection might break, but there should be some feedback.

• Components: ColorPicker "vibrates" when moving the circle slowly #35675
• Components: ColorPicker closes randomly on occasions when trying to interact with it #35677

• Site logo placeholder graphic is not rendered properly in the site editor.
• The template dropdown has template parts with no names when they don't belong to an area. Reported in When editing a template part in isolation the Areas UI is surfacing general template parts #35587.

• Buttons inside groups are misaligned. (Might be theme related.)

• Disabling theme editor styles in preferences makes some elements in the page load with default colors and not the current color scheme.

• The sibling inserter repositioning, together with the animation, makes it jump around.

• The amount of lines shown in the site editor to distinguish active focus, hover focus, current template part focus, etc, is wild. We need to reduce this.

• There's also a weird dotted outline on the site block.

• More blocks with dotted outlines that don't seem appropriate.

• Search in navigation menus is super awkward. It should be possible to get an icon only button that expands inline or in an overlay. This should likely also be the default. The initial insertion state, in particular, is a terrible experience (Search: Hide label when inserted in Navigation block #36026):

• Menu settings (called Display) should come before the Typography supports and should probably not be in a panel at all (not collapsible).

• Typography: default size looks "unset".