Navigation block: Consider reducing the interface on clicking in a menu item

[karmatosed]

Currently, when you click to add an item you see this:

I would suggest that reducing what is shown by default to adding a link. Then when that's done the rest of the toolbar and items could appear. I know this isn't a behaviour we use everywhere right now but what we present is a lot for someone to experience.

[mapk]

I'd also really like to see that input field to be larger than 2 characters by default.

[karmatosed]

I don't think the input is the issue here though. For me, it's showing everything on at once. For example, reducing the toolbar back and having it just load a link interface would be better for the cognitive load. I also don't see this as an input field as it's like typing for me.

[mapk]

I don't think the input is the issue here though.

Nevertheless it's still an issue. I'm happy to create a new one if you'd like.

[karmatosed]

@mapk absolutely, saves it being hidden in this.

[WunderBart]

Sounds good to me, @karmatosed! Also IMO, when the toolbar is visible it suggests that the block content/input is currently active. In our case (right after clicking the ⊕ button) it actually isn't - the popup input is. It becomes obvious once you start writing which will make the toolbar disappear instantly, so for me it's another reason to hide it by default. Any mouse movement brings the toolbar back, so it should not make anyone's life harder, I guess?

I'd be happy to take this one on!

[WunderBart]

@karmatosed I'm holding off my work (#19531, #19561) on this one as I don't believe there's a reliable way to implement this enhancement at this point (please see #19531 (comment) and #19561 (comment)). Let's get back to it once #19344 is in.

[mtias]

@WunderBart I'd like to try the "absorb child block toolbar in the parent" setting for this one.

[tellthemachines]

@WunderBart I'd like to try the "absorb child block toolbar in the parent" setting for this one.

@mtias could you elaborate on this approach, or point us to where it was discussed?

I'm wondering if it still makes sense to have this issue as specific to the Navigation work, given the comments here and here point to this requiring a solution consistent between all blocks.

[mtias]

@tellthemachines this work: #18440

And the __experimentalCaptureToolbars API.

[getdave]

Glad the __experimentalCaptureToolbars got used :)

[draganescu]

It looks like #18440 closed this issue.