- Issue created by @nod_
- π¬π§United Kingdom catch
It seems likely that this won't be the last blocker to deprecating layout builder, so I think it would make sense to remove the layout builder UI dependency as a by-product of the UX improvements, and then only have to do the implementation once (or at least, not definitely have to do it twice).
We briefly discussed that https://github.com/SortableJS/Sortable might be a good fit here, since this only needs 1d drag and drop, and doesn't need/want a table. Sortable is already in core.libraries.yml so no new dependency.
- πͺπΈSpain ckrina Barcelona
Huge +1 to this. As discussed with Navigation maintainers and several core committers the existing UI doesnβt meet the UX standards we should have.
- π¬π§United Kingdom catch
Adding a reference to #3452724-78: Add aria-label attribute to navigation menu blocks β - with the existing UI, the 'fake' navigation bar that you edit has the same aria labels as the 'real' navigation bar which could be additionally confusing for people using screenreaders.