\n\u003C/UCard>\n```\n\n### Description\n\nIf using a UTable component on a background that isn't the default neutral color the bg-color of the thead is visible.\n\n\n\n\n\n_A little bit easier to see with white Background_\n\n\n\n\nMaybe this is a wanted behavior. So if so please ignore and close the issue.\nI know sometimes you want a background color in the headlines. But sometimes you don't want them.\nAnyways if this is a wanted behavior, then maybe this issue will help those who don't want a background color and are looking for a solution.\n\n### Additional context\n\nCould be fixed by adding:\n```vue\n:ui=\"{\n thead: 'bg-unset'\n}\"\n```\nto the `\u003CUTable>` tag\n\n\n\n### Logs\n\n```shell-script\n-\n```",[2873,2876,2877],{"name":2874,"color":2875},"bug","d73a4a",{"name":2860,"color":2861},{"name":2878,"color":2879},"triage","ffffff",3607,"Background-Color for UTable","2025-03-18T15:08:25Z","https://github.com/nuxt/ui/issues/3607",0.75458294,{"description":2886,"labels":2887,"number":2891,"owner":2863,"repository":2864,"state":2865,"title":2892,"updated_at":2893,"url":2894,"score":2895},"### Environment\n\nNuxt UI pro v 3.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input-menu#control-search-term\n\n### Description\n\nHello, \n\nI am reopening an issue based on https://github.com/nuxt/ui/issues/3782\n\nI still have an issue on the InputMenu that filters with the default value.\n\nAs a reproduction : we can see the same behavior I am facing in the documentation : https://ui.nuxt.com/components/input-menu#control-search-term . \n\n1) => The first click on InputMenu shows only the seacherd term (here Backlog)\n2) => If I close the popover and reopen it a second time, it shows the entire list.\n\nI tried the :reset-search-term-on-select=\"false\" , it allows to display the entire list at 1st click but it leads to not showing the default selected value (the placeholder is displayed).\n\nActually, I am looking to display the entire list at first click, even if a value is already selected.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2888,2889,2890],{"name":2874,"color":2875},{"name":2860,"color":2861},{"name":2878,"color":2879},3993,"InputMenu Clear Search on Select at first click","2025-04-27T12:37:04Z","https://github.com/nuxt/ui/issues/3993",0.76385415,{"description":2897,"labels":2898,"number":2899,"owner":2863,"repository":2900,"state":2865,"title":2901,"updated_at":2902,"url":2903,"score":2904},"Hi team, \r\n\r\nThis time i founded this vulnerability in your website: \r\nhttps://nuxtjs.org/\r\n\r\n\r\n\r\nClick jacking (User Interface redress attack, UI redress attack, UI redressing) is a malicious technique of tricking a Web user into clicking on something different from what the user perceives they are clicking on, thus potentially revealing confidential information or taking control of their computer while clicking on seemingly innocuous web pages.\r\n\r\nThe server didn't return an X-Frame-Options header which means that this website could be at risk of a click jacking attack. The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a \u003Cframe> or \u003Ciframe>. Sites can use this to avoid click jacking attacks, by ensuring that their content is not embedded into other sites.\r\n\r\nThis vulnerability affects Web Server.\r\n\r\nHere are the steps to reproduce the vulnerability:\r\n\r\n1.open notepad and paste the following code.\r\n\u003C!DOCTYPE HTML>\r\n\u003Chtml lang=\"en-US\">\r\n\u003Chead>\r\n\u003Cmeta charset=\"UTF-8\">\r\n\u003Ctitle>i Frame\u003C/title>\r\n\u003C/head>\r\n\u003Cbody>\r\n\u003Ch3>This is clickjacking vulnerable\u003C/h3>\r\n\u003Ciframe src=\" https://nuxtjs.org/ \" frameborder=\"2 px\" height=\"500px\" width=\"500px\">\u003C/iframe>\r\n\u003C/body>\r\n\u003C/html>\r\n\r\n2.save it as \u003Canyname>.html eg s.html\r\n\r\n3.and just simply open that...\r\n\r\nOR\r\nCopy the link below and paste on your updated browser (Chrome,Firefox).\r\nhttps://clickjacker.io/test?url=https://nuxtjs.org/\r\nAs far as i know this data is enough to prove that your site is vulnerable to Click jacking\r\naccording to OWASP its more than enough.\r\n\r\nhttps://www.owasp.org/index.php/Testing_for_Clickjacking_(OWASP-CS-004) \r\n\r\nSOLUTION: \r\n\r\nhttps://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet\r\n\r\nCheck this out and here is the solution for that.\r\n \r\n\r\nI Hope that you will fix this issue as soon as possible. Looking forward to hear from you. Thank you\r\n\r\nSincerely,\r\nHassan Raza\r\n",[],1456,"nuxt.com","Vulnerability type Click Jacking","2023-12-27T17:14:15Z","https://github.com/nuxt/nuxt.com/issues/1456",0.7650374,{"description":2906,"labels":2907,"number":2913,"owner":2863,"repository":2863,"state":2865,"title":2914,"updated_at":2915,"url":2916,"score":2917},"### Describe the feature\r\n\r\nNow that I think I understand composables better, especially useFetch, I see myself using it everytime I communicate to my api. Even when posting a form, because I like the out of the box reactive properties it provides.\r\n\r\nAnd now that Nuxt 3.11 adds `clear()` I feel its complete.\r\n\r\nI often end up doing this:\r\n\r\n```js\r\nconst formData = reactive({\r\n firstName: 'Peter',\r\n lastName: 'Griffin',\r\n ...\r\n});\r\n\r\nconst { status, execute: submit, clear, error } = useFetch('...', {\r\n watch: false,\r\n immediate: false,\r\n \r\n body: formData,\r\n method: 'POST',\r\n});\r\n\r\nonBeforeMount(clear); // maybe theres an even better way to automatically clear things up?\r\n```\r\n\r\nI propose to add a new composable, analog to `useLazyFetch`.\r\n\r\nIt could be named `useManualFetch`, `usePostFetch` (`usePost`?) or `useSubmitFetch` (`useSubmit`?)\r\n\r\nAnd it could be used like this:\r\n\r\n```\r\nconst formData = reactive({ ... });\r\nconst { status, error, execute: submit } = useSubmit('...', formData);\r\n```\r\n\r\nMaybe `lazy: true` and `server: false` is also a good default here? I'm not at all familiar enough with SSR and nitro at this point–\r\n\r\nI know I could make (and have made) that composable myself, but I think this is a good thing to offer out of the box to everybody.\r\n\r\nWhat do you think?\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [x] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2908,2910],{"name":2857,"color":2909},"8DEF37",{"name":2911,"color":2912},"discussion","538de2",26306,"adding useManualFetch / usePostFetch / useSubmitFetch composable","2024-06-30T11:05:09Z","https://github.com/nuxt/nuxt/issues/26306",0.76526535,{"description":2919,"labels":2920,"number":2925,"owner":2863,"repository":2864,"state":2926,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Description\n\nMy app uses a LOT of filters, and with UI v2, I had these:\n\n```\n\u003CUSelect :items=\"items\" placeholder=\"Filter by tags\" v-model=\"tagFilter\" />\n\n// filter by tags\nconst items = [\n {\n label: \"Show all tags\",\n value: \"\"\n },\n {\n label: \"Only Red Tags\",\n value: \"red\"\n },\n {\n label: \"Only Green Tags\",\n value: \"green\"\n }\n]\n\nconst tagFilter = ref(null)\n```\n\nbut in v3 I now get this error:\n\n> Error: A \u003CSelectItem /> must have a value prop that is not an empty string. This is because the Select value can be set to an empty string to clear the selection and show the placeholder.\n\nHow would I add this option in?",[2921,2924],{"name":2922,"color":2923},"question","d876e3",{"name":2860,"color":2861},3647,"closed","How do I use an empty string with a USelect value?","2025-03-21T21:54:20Z","https://github.com/nuxt/ui/issues/3647",0.701366,{"description":2932,"labels":2933,"number":2939,"owner":2863,"repository":2864,"state":2926,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nFor example if I use something like this,\n\n`const items=[{label:'option 1', value:1},{label:'option 2',value:2}]`\n\n the value that is always assigned is string '1'\n\n`const typeData=ref(1)`\n\n ``\n \u003CUSelect v-model=\"form.productType\" class=\"w-full\" :items=\"items\" />\n```\n",[2934,2937,2938],{"name":2935,"color":2936},"duplicate","cfd3d7",{"name":2922,"color":2923},{"name":2860,"color":2861},2924,"[v3] select type only string?","2024-12-17T15:56:57Z","https://github.com/nuxt/ui/issues/2924",0.71217805,{"description":2945,"labels":2946,"number":2954,"owner":2863,"repository":2863,"state":2926,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Describe the feature\r\n\r\nAfter https://github.com/nuxt/nuxt/pull/23600 landed I wondered - couldn't we support the same for `useState`? 🤔\r\n\r\nWhich is: Give the users the option to use a `shallowRef` instead of a `ref` as underlying reactive structure\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2947,2948,2951],{"name":2911,"color":2912},{"name":2949,"color":2950},"3.x","29bc7f",{"name":2952,"color":2953},"pending triage","E99695",24068,"Using `shallowRef` for `useState`","2023-11-01T16:15:59Z","https://github.com/nuxt/nuxt/issues/24068",0.7500016,{"description":2960,"labels":2961,"number":2964,"owner":2863,"repository":2863,"state":2926,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Describe the feature\n\nThe repo for the custom usefetch composable example is missing. \r\n\r\nSee: https://nuxt.com/docs/examples/advanced/use-custom-fetch-composable\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2962,2963],{"name":2949,"color":2950},{"name":2952,"color":2953},21894,"Missing usefetch composable example in docs","2023-07-03T07:58:41Z","https://github.com/nuxt/nuxt/issues/21894",0.7500057,{"description":2970,"labels":2971,"number":2972,"owner":2863,"repository":2973,"state":2926,"title":2974,"updated_at":2975,"url":2976,"score":2977},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.22.5`\n- Nitro Version: `2.11.5`\n- Package Manager: `bun@1.2.4`\n- Builder: `-`\n- User Config: `runtimeConfig`, `modules`, `app`, `site`, `sitemap`, `robots`, `css`, `icon`, `image`, `ui`, `devtools`, `future`, `unhead`, `compatibilityDate`\n- Runtime Modules: `@nuxt/ui@3.0.0-beta.3`, `@pinia/nuxt@0.10.1`, `@nuxt/scripts@0.10.5`, `@nuxt/image@1.9.0`, `@nuxtjs/seo@2.2.0`\n- Build Modules: `-`\n\n### Reproduction\n\nnda\n\n### Describe the bug\n\nnr dev\n$ nuxt dev\nNuxt 3.16.0 with Nitro 2.11.5 nuxi 8:23:08 PM\n 8:23:08 PM\n ➜ Local: http://localhost:3003/\n ➜ Network: use --host to expose\n\n ➜ DevTools: press Shift + Option + D in the browser (v2.2.1) 8:23:10 PM\n\n\n✔ Nuxt Icon loaded local collection elfi with 70 icons 8:23:10 PM\nℹ Running with compatibility version 4 nuxt 8:23:10 PM\n✔ Vite client built in 190ms 8:23:11 PM\n✔ Vite server built in 528ms 8:23:12 PM\n\n[nitro 8:23:14 PM] ERROR Error: Could not load /\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs (imported by node_modules/nuxt-og-image/dist/runtime/server/og-image/satori/instances.js): ENOENT: no such file or directory, open '/\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs'\n\n\nundefined\n\n### Additional context\n\nUpgraded by \"nuxi upgrade -f\" from 3.15.4 and couldn't able to start properly with provided error.\nTried with unhead flag in nuxt.config - same error\n```\nunhead: {\n legacy: true,\n }\n```\n\n### Logs\n\n```shell-script\n\n```",[],414,"scripts","Nuxt 3.16.0 won't start properly nor dev nor build","2025-03-07T18:58:03Z","https://github.com/nuxt/scripts/issues/414",0.75320417,["Reactive",2979],{},["Set"],["ShallowReactive",2982],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4hn3vqUfEx4NIoHW8k7OXALM9aELwORC4zTW-ZBccmM":-1},"/nuxt/ui/3393"]