Environment
|
|
| Operating system |
macOS 25.3.0 |
| CPU |
Apple M3 (8 cores) |
| Node.js version |
v22.17.0 |
| nuxt/cli version |
3.35.2 |
| Package manager |
pnpm@10.18.3 |
| Nuxt version |
4.4.6 |
| Nitro version |
2.13.4 |
| Builder |
vite@7.3.3 |
| Config |
$development, $production, $test, app, compatibilityDate, css, devServer, devtools, eslint, experimental, fonts, hub, icon, image, linkChecker, modules, nitro, ogImage, pagesPlus, robots, runtimeConfig, schemaOrg, scripts, sentry, seo, site, sitemap, sourcemap, testUtils, typescript, ui, vite |
| Modules |
@vueuse/nuxt@14.1.0, @nuxt/fonts@0.14.0, @nuxt/eslint@1.15.2, @nuxt/image@2.0.0, @builder.io/sdk-vue/nuxt@5.2.2, @nuxt/scripts@0.13.2, @nuxt/ui@4.7.1, @nuxthub/core@0.9.1, @pinia/nuxt@0.11.3, nuxt-pages-plus@1.0.0-beta.4, nuxt-auth-utils@0.5.29, @sentry/nuxt/module@10.49.0, @nuxt/test-utils/module@3.23.0, nuxt-og-image@6.0.7, @nuxtjs/seo@3.3.0, @nuxtjs/device@4.0.0, @atoms-studio/nuxt-swiftsearch@0.9.11 |
Is this bug related to Nuxt or Vue?
Nuxt
Package
v4.x
Version
v4.7.1
Reproduction
<UInputMenu
v-model="value"
:items="items"
autocomplete="address-line1"
/>
Type 'string' is not assignable to type 'boolean | undefined'.
Description
PR #6026 added an autocomplete: boolean prop to UInputMenu to switch between Combobox and Autocomplete modes. Unfortunately the name collides with the standard HTML autocomplete attribute used for browser autofill (address-line1, cc-number, one-time-code, etc.). Other Nuxt UI form components (UInput, USelect, UTextarea) let this attribute fall through to the inner element, so the inconsistency is surprising.
Impact:
- TS error for any v3 code that was passing the HTML attribute.
- Silent UX regression for browser autofill, password managers, OTP autofill, etc. Only on
UInputMenu.
- No public API to set the HTML autocomplete attribute on the inner input; consumers have to reach for the exposed inputRef and call setAttribute imperatively.
Additional context
No response
Logs
Environment
macOS 25.3.0Apple M3 (8 cores)v22.17.03.35.2pnpm@10.18.34.4.62.13.4vite@7.3.3$development,$production,$test,app,compatibilityDate,css,devServer,devtools,eslint,experimental,fonts,hub,icon,image,linkChecker,modules,nitro,ogImage,pagesPlus,robots,runtimeConfig,schemaOrg,scripts,sentry,seo,site,sitemap,sourcemap,testUtils,typescript,ui,vite@vueuse/nuxt@14.1.0,@nuxt/fonts@0.14.0,@nuxt/eslint@1.15.2,@nuxt/image@2.0.0,@builder.io/sdk-vue/nuxt@5.2.2,@nuxt/scripts@0.13.2,@nuxt/ui@4.7.1,@nuxthub/core@0.9.1,@pinia/nuxt@0.11.3,nuxt-pages-plus@1.0.0-beta.4,nuxt-auth-utils@0.5.29,@sentry/nuxt/module@10.49.0,@nuxt/test-utils/module@3.23.0,nuxt-og-image@6.0.7,@nuxtjs/seo@3.3.0,@nuxtjs/device@4.0.0,@atoms-studio/nuxt-swiftsearch@0.9.11Is this bug related to Nuxt or Vue?
Nuxt
Package
v4.x
Version
v4.7.1
Reproduction
Description
PR #6026 added an
autocomplete: booleanprop toUInputMenuto switch between Combobox and Autocomplete modes. Unfortunately the name collides with the standard HTMLautocompleteattribute used for browser autofill (address-line1, cc-number, one-time-code, etc.). Other Nuxt UI form components (UInput,USelect,UTextarea) let this attribute fall through to the inner element, so the inconsistency is surprising.Impact:
UInputMenu.Additional context
No response
Logs