",[1998,2001,2004],{"name":1999,"color":2000},"enhancement","a2eeef",{"name":2002,"color":2003},"v3","49DCB8",{"name":2005,"color":2006},"triage","ffffff",3270,"[Feature request] Toast hide progress in app.config","2025-02-09T17:11:11Z","https://github.com/nuxt/ui/issues/3270",0.73078686,{"description":2013,"labels":2014,"number":2015,"owner":1988,"repository":2016,"state":1990,"title":2017,"updated_at":2018,"url":2019,"score":2020},"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.73396295,{"description":2022,"labels":2023,"number":2028,"owner":1988,"repository":1989,"state":1990,"title":2029,"updated_at":2030,"url":2031,"score":2032},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.15.1\n- Nuxt Version: 3.14.159\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.14.3\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n\n### Version\n\nv2.18.6\n\n### Reproduction\n\nGo here:\n\nhttps://ui.nuxt.com/components/tabs#default-index\n\nReload the page\n\n### Description\n\nWhen tabs have an initial index other than `0` they visually transition from the left tab to the index / v-model # tab.\n\nHappy to PR this.\n\n### Additional context\n\n\n\n### Logs\n\n```shell-script\n\n```",[2024,2027],{"name":2025,"color":2026},"bug","d73a4a",{"name":2005,"color":2006},3084,"[Tabs] non-0 `index` / `v-model` always transitions from 0","2025-01-13T13:45:29Z","https://github.com/nuxt/ui/issues/3084",0.7420994,{"description":2034,"labels":2035,"number":2038,"owner":1988,"repository":1989,"state":2039,"title":2040,"updated_at":2041,"url":2042,"score":2043},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v18.20.2`\n- Nuxt Version: `3.14.159`\n- CLI Version: `3.15.0`\n- Nitro Version: `2.10.4`\n- Package Manager: `pnpm@9.0.6`\n- Builder: `-`\n- User Config: `default`\n- Runtime Modules: `@nuxt/eslint@0.7.1`, `@nuxt/ui@3.0.0-alpha.7`\n- Build Modules: `-`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.7\n\n### Reproduction\n\nhttps://github.com/juretopolak/nuxt-ui3-toasts\n\nhttps://codesandbox.io/p/github/juretopolak/nuxt-ui3-toasts/main\n\n### Description\n\nI’ve noticed an issue where toasts fail to render properly when multiple toasts are triggered in quick succession, such as within a loop. This leads to unexpected behavior, such as:\n\n\t•\tSome toasts not appearing at all.\n\t•\tOverlapping toasts.\n\nIn the reproduction, every time a button is clicked 2 toasts should appear.\n\n### Additional context\n\nhttps://github.com/user-attachments/assets/161918f9-7ab2-45d9-aebb-493977ebbc52\n\n\n### Logs\n\n```shell-script\n\n```",[2036,2037],{"name":2025,"color":2026},{"name":2002,"color":2003},2686,"closed","Problem with multiple toasts in succession","2025-01-24T14:24:11Z","https://github.com/nuxt/ui/issues/2686",0.70938766,{"description":2045,"labels":2046,"number":2049,"owner":1988,"repository":1989,"state":2039,"title":2050,"updated_at":2051,"url":2052,"score":2053},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.9.0\n- Nuxt Version: 3.13.1\n- CLI Version: 3.13.1\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: devtools, modules, css, ui, colorMode, compatibilityDate, icon, sourcemap, experimental, nitro, future, pwa, routeRules, spaLoadingTemplate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, @vueuse/nuxt@10.11.1, @nuxtjs/mdc@0.6.1, @formkit/auto-animate/nuxt@0.8.2, @vite-pwa/nuxt@0.10.5\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\n`style tag`\n\n`Use`\n\n`debug`\n\n\n\n### Description\n\nSorry, I don't know if it's a bad configuration on my part, however the styles in which I use @apply don't work for me.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2047,2048],{"name":2025,"color":2026},{"name":2002,"color":2003},2763,"postcss style not applying","2024-12-05T13:48:59Z","https://github.com/nuxt/ui/issues/2763",0.7165612,{"description":2055,"labels":2056,"number":2059,"owner":1988,"repository":2016,"state":2039,"title":2060,"updated_at":2061,"url":2062,"score":2063},"Hover effect https://www.notion.so/nuxt/Hover-effect-3c4180c18f5b4cea91e921736496328e",[2057],{"name":2025,"color":2058},"ff281a",1086,"[Review] UCard","2023-02-15T12:31:06Z","https://github.com/nuxt/nuxt.com/issues/1086",0.7295644,{"description":2065,"labels":2066,"number":2067,"owner":1988,"repository":2068,"state":2039,"title":2069,"updated_at":2070,"url":2071,"score":2072},"\r\nI get warn: `Avoid app logic that relies on enumerating keys on a component instance. The keys will be empty in production mode to avoid performance overhead.` when I use an icon component and use multiple slots at the same time.\r\n\r\n# Replication:\r\nnuxt.config.ts\r\n```javascript\r\nexport default defineNuxtConfig({\r\n devtools: { enabled: true },\r\n modules: ['@nuxt/content', \"nuxt-icon\"],\r\n content: {\r\n documentDriven: {\r\n trailingSlash: false\r\n }\r\n }\r\n})\r\n```\r\ncomponents/content/ComponentWithIcon.vue\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n Component with icon:\r\n \u003CIcon name=\"bxl:python\" class=\"w-8 h-8\" />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\ncomponents/content/Container.vue:\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nlayouts/full.vue:\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"custom-layout\">\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\ncontent/index.md:\r\n```markdown\r\n---\r\nlayout: 'full'\r\n---\r\n\r\n:component-with-icon\r\n\r\n::container\r\nSlot nr 1\r\n::::container\r\nSlot nr 2\r\n::::\r\n::\r\n```\r\n\r\nThis bug prevents the site from being used in development mode due to the infinity loop. The problem does not occur in the latest beta version of nuxt-icon, but in the original project I use nuxt-ui, which uses the old version \r\n",[],157,"icon","Infinite WARN loop with slots and nuxt-content","2024-09-06T11:17:31Z","https://github.com/nuxt/icon/issues/157",0.73809737,{"description":2074,"labels":2075,"number":2081,"owner":1988,"repository":2016,"state":2039,"title":2082,"updated_at":2083,"url":2084,"score":2085},"Update [Webreinvent partner page](https://nuxt.com/support/agencies/webreinvent) with content below :\n\nWebReinvent has 12+ years of experience building software and a team of 50+ software professionals including software developers, UI/UX designers, testers, DevOps, project managers, etc. The team is well-versed in the Nuxt ecosystem and has delivered multiple high-performance web apps, dashboards, real-time apps, multi-tenant SaaS applications, etc.\n\nWe are one of the most process-driven companies and we love to follow industry standards. Some of them are managing git repo, code review/audits, deploying new releases via CI/CD, automated software testing, maintaining detailed technical documentation, application performance monitoring, etc. We have been delivering MVP to enterprise-level software products from startup to MSME.\n\nContact us to build your MVP fast or migrate your legacy software to Nuxt or maintain your existing software or scale your software to the enterprise level. We're here to help.\n",[2076,2078],{"name":1999,"color":2077},"1ad6ff",{"name":2079,"color":2080},"marketing","f5c828",1156,"Update Webreinvent partner page","2023-06-06T12:14:42Z","https://github.com/nuxt/nuxt.com/issues/1156",0.743056,{"description":2087,"labels":2088,"number":2095,"owner":1988,"repository":1988,"state":2039,"title":2096,"updated_at":2097,"url":2098,"score":2099},"### Environment\n\nReproduced with minimum Nuxt 3 environment on StackBlitz, as well as locally on a MacOS computer with Node 19.\n\n### Reproduction\n\nLink can be found here: https://stackblitz.com/edit/github-umca8w?file=app.vue\r\n\r\nA `\u003CTitle>` component will use a comment, if specified first, as the actual title.\r\n\r\n```vue\r\n\u003CTitle>\u003C!-- this will be the title --> not this\u003C/Title>\r\n```\n\n### Describe the bug\n\nA `\u003CTitle>` component will read the first element, even if it is a comment. This causes comments to be displayed as a title, not the intended text afterwords.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2089,2092],{"name":2090,"color":2091},"3.x","29bc7f",{"name":2093,"color":2094},"🍰 p2-nice-to-have","0E8A16",19716,"Head (\u003CTitle>) components should validate input better","2023-06-17T21:37:07Z","https://github.com/nuxt/nuxt/issues/19716",0.74730897,["Reactive",2101],{},["Set"],["ShallowReactive",2104],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"N4YMi38Of8D7hJCCXhdpwbD6YdXjZFOPAJwKkf_3QF0":-1},"/nuxt/ui/3103"]