The navigation keyboard shortcuts found in Chome (i.e. cmd + arrow left/right to navigate back or forward) are not working.
Listening to keyboard events (using javascript) is not working either(i.e. I've registered a listener on a specific key press to launch the video element in fullscreen but it doesn't work either).

Suggestion

WordPress core recently added this to the navwalker:
https://core.trac.wordpress.org/ticket/43290

Without adding these attributes google audit flags as a security risk, suggested change for class-wp-bootsrap-navwalker.php:

`//$atts['rel'] = ! empty( $item->xfn ) ? $item->xfn : '';

	if ( '_blank' === $item->target && empty( $item->xfn ) ) {
		$atts['rel'] = 'noopener 

The problem is that this UIWindow stays in stack after Yoshi has been disappeared as Yoshi never removes this UIWindow from the stack and never makes main application's UIWindow keyAndVisible again. Yoshi just removes it reference to the UIWindow it created (see lines 100 and 111). It influences long term behaviour of the main application and also influences other libraries that creates UIWindow.

Currently wagtailmenus makes a database query to identify the page IDs of ancestors, and keeps it around in the context to help figure this out.

If we can work this out without a query, we should definitely do so. And with active class derivation becoming more efficient, we should just go ahead and apply it every time, and not make it optional.

There is documentation for adding attributes to menu items, but how about the menu parent element?
I tried doing a $menu->attribute, but that did not work.

I would like to add class names to the

, I propose adding the same capabilities to menu as there are for item. IE:
$menu = Menu::make(...)->attribute(['class'=>'navbar-nav','id'=>'main-nav'])
would yield

Currently, examples cannot be easily built after cloning the repo or on CI. Add a new .csproj containing all the examples and make the necessary changes so only one plugin needed (i.e. using commands to start each example).
Additionally, build the examples on CI.

venu#unregisterAll should be renamed to venu#clear (it actually clears/deletes all menu items).

Further, more argument types should be supported in venu#clear(arg).
arg may be:

• a menu/submenu
• name (string) of a menu/submenu
• () empty -> clear all (like venu#unregisterAll currently)