InputMenu does not support Home and End key navigation inputs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.1k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 57
Description
Environment
| Operating system | Windows 10.0.26200 |
| CPU | Intel(R) Core(TM) i9-10940X CPU @ 3.30GHz (28 cores) |
| Node.js version | v24.3.0 |
| nuxt/cli version | 3.31.1 |
| Package manager | pnpm@10.24.0 |
| Nuxt version | 4.2.1 |
| Nitro version | 2.12.9 |
| Builder | vite@7.2.6 |
| Config | apollo, compatibilityDate, css, devServer, devtools, i18n, modules, runtimeConfig |
| Modules | @nuxt/ui@4.2.1, @nuxtjs/i18n@10.2.1, @nuxtjs/apollo@5.0.0-alpha.15, @vueuse/nuxt@14.1.0 |
Is this bug related to Nuxt or Vue?
Nuxt
Package
v4.x
Version
v4.2.1
Reproduction
https://ui.nuxt.com/docs/components/input-menu#usage
Description
When going to https://ui.nuxt.com/docs/components/input#usage and type something into the first example, and then use the Home and End keys, the cursor jumps to the start or the end of the input value.
But when using a InputMenu, this behavior is not present.
Go to https://ui.nuxt.com/docs/components/input-menu#usage and click inside the first field where the term Backlog is currently present.
Try the Home and End keys like before. => Nothing happens.
Additional context
No response
Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the InputMenu usage example in the linked Nuxt UI documentation and compare its Home and End key behavior with the Input example. Trace the InputMenu component entry point, then verify that those keys move the cursor to the start and end of the value without breaking the existing input behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100