Menu should not be focusable and doesn't need to support events

[NickClark]

📑 Description

Currently the SVG image inside the NavHamburger get's focused as well. Since the Menu component doesn't need to be focused in this case, the SVG needs it's role changed and made un-focusable so that the button can retain the focus.

After focus Current:

After focus with MR:

Status

• Completed

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• I have checked the page with https://validator.unl.edu/
• All the tests have passed
• My pull request is based on the latest commit (not the npm version).

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
flowbite-svelte	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 1, 2023 11:45am
flowbite-svelte-update	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 1, 2023 11:45am

[Ashvith10]

@NickClark is this about the inconsistent behavior between the Svelte component and the Tailwind component, where clicking on an SVG does not trigger the outline in the former, but works on the latter?

[NickClark]

@Ashvith10 I started this because it looked horrible, but now that I'm comparing, my fix does seem to make it look and act like the normal, non-Svelte, Flowbite example.

[shinokada]

Since it has {...$$restProps}, why don't you just add focusable="false"?

[shinokada]

I close the PR for now.
Thank you for your contribution.