[kwy404]

Description

• Root cause: Menu#_handleSubmenuKeydown() handles Home and End for any key target. When the target is the toggle, closest('.menu') returns null, because the toggle is outside the menu. The handler calls preventDefault() and then passes null to _getItemsInMenu(), which throws TypeError: Illegal invocation.
• Fix: return early when the key target is not inside a .menu. Home and End keep their default action on the toggle, and nothing throws. Inside a menu (items, submenu toggles, a menu moved to container), Home and End still move focus to the first or last item.
• Test: should leave Home and End to the browser on the toggle in js/tests/unit/menu.spec.js presses Home and End on the toggle with the menu closed and open. Before the fix it fails with expected true to be exactly false and Vitest reports TypeError: Illegal invocation. After the fix it passes.
• Ran npm run js-test (37 files, 1471 tests pass; 1470 on main), npm run js-lint (0 errors, same 15 warnings as main) and npm run js-typecheck.

Motivation & Context

To reproduce: focus any [data-bs-toggle="menu"] button, then press Home or End. Chrome logs Uncaught TypeError: Illegal invocation (other browsers word it differently), and the key does nothing because its default action is prevented. This also happens on nav links that toggle a menu.

I kept Home and End as plain browser keys on the toggle instead of making them jump into the open menu. The docs list them as moving between menu items, the v5 Dropdown never handled them on the toggle, and the ARIA menu button pattern only gives the button Enter, Space and the arrow keys. Happy to switch to focusing the first or last item if you prefer that.

Type of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (non-breaking change)
• Breaking change (fix or feature that would change existing functionality)

Checklist

• I have read the contributing guidelines
• My code follows the code style of the project (using npm run lint)
• My change introduces changes to the documentation
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

Live previews

Not applicable, JavaScript only change.

Related issues

None.