\n```\n\n### Description\n\nThe issue occurs both when I run the app in development mode and when I build it for production. I tested it on Safari (Mac and iPhone) and Chrome (iPhone only). On the first page load, the animation works fine, but when I reload the page, the animation stops. However, when the component where it is used updates, the icon state changes (still without animation). \n\nHere I placed some icons randomly in the pages to show the problem and when it occurs:\n\nhttps://github.com/user-attachments/assets/ca9772d8-61bb-47da-9b9e-38cbb8d5796c\n\n).",[],361,"icon","Icon is not animating correctly","2025-02-23T14:06:29Z","https://github.com/nuxt/icon/issues/361",0.69861466,{"description":2014,"labels":2015,"number":2022,"owner":1988,"repository":2023,"state":1990,"title":2024,"updated_at":2025,"url":2026,"score":2027},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nAFAIK there is currently no documented way to prevent the popover from opening automatically through click or hover.\n\nExample API:\n\n```\n\u003CUPopover mode=\"manual\">\n \u003CUButton>I don't do anything\u003C/UButton\n\u003C/UPopover>\n```\n\n### Additional context\n\nRelated to #721 (but not fixed)",[2016,2019],{"name":2017,"color":2018},"enhancement","a2eeef",{"name":2020,"color":2021},"v3","49DCB8",2925,"ui","Popover manual mode with no click nor hover","2024-12-21T16:25:47Z","https://github.com/nuxt/ui/issues/2925",0.7157461,{"description":2029,"labels":2030,"number":2031,"owner":1988,"repository":1989,"state":2032,"title":2033,"updated_at":2034,"url":2035,"score":2036},"It seems that v0.2.2 is the latest available release according to npm and Github. However there have been 18 commits to `main` since then. Is this a deliberate choice **not** to release or some automation that has stopped working?\r\nhttps://github.com/nuxt/test-utils/compare/v0.2.2...main\r\n\r\n~As an aside I am getting 500 errors from the nuxt server which is why I am digging further into things.~ Removed to keep the Issue focused ❤️ ",[],485,"closed","Stale releases","2023-12-02T00:13:13Z","https://github.com/nuxt/test-utils/issues/485",0.6676781,{"description":2038,"labels":2039,"number":2043,"owner":1988,"repository":2008,"state":2032,"title":2044,"updated_at":2045,"url":2046,"score":2047},"Hello,\r\n\r\nI was wondering whether there is a way to allow users to tell whether they want to allow iconify cookies or not. \r\nAfter all, for GDPR they should be able to control this behaviour!",[2040],{"name":2041,"color":2042},"question","d876e3",94,"Iconify cookies","2024-12-21T12:20:21Z","https://github.com/nuxt/icon/issues/94",0.6941524,{"description":2049,"labels":2050,"number":2053,"owner":1988,"repository":2023,"state":2032,"title":2054,"updated_at":2055,"url":2056,"score":2057},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nI've noticed that links (\\\u003Ca\\> tags) created with `UButton` contain a lot of unnecessary styling related to the button itself, disabled and enabled state. Given that for anchors there is no `disabled` property in the HTML specification, this means that out of the following styles:\n```\nrounded-[calc(var(--ui-radius)*1.5)] font-medium inline-flex items-center focus:outline-none transition-colors px-2.5 py-1.5 text-sm gap-1.5 ring ring-inset ring-[var(--ui-primary)]/50 text-[var(--ui-primary)] hover:bg-[var(--ui-primary)]/10 focus-visible:ring-2 focus-visible:ring-[var(--ui-primary)]\n```\n\nAt the very least, these can be removed:\n\n```\ndisabled:cursor-not-allowed aria-disabled:cursor-not-allowed disabled:opacity-75 aria-disabled:opacity-75 disabled:bg-transparent aria-disabled:bg-transparent dark:disabled:bg-transparent dark:aria-disabled:bg-transparent\n```\n\nThis is quite a reduction in classes and can make a moderate difference in total page size and even web vitals scores, especially if there are a lot of links on the page created with `UButton` (which is very likely given the customization UButton provides with icons, variants, colors, and more)\n\nIn order to make this work, the classes that rely on disabled state would likely need to be extracted into a separate place in the theme, which tailwind-variants will then need to merge if there is no `to` property present.\n\nYou might be asking why, given that technically people can rely on it to prevent navigation until a certain condition. But the answer to that is that restricting links like that is generally bad practice and can be circumvented pretty easily. It's not meant to be a security feature and it also lacks in terms of functional purpose.\n\nI'll check to see what I can do about it, but I thought sharing it here would be more beneficial in case someone will be faster than me in preparing a PR for this =)",[2051,2052],{"name":2041,"color":2042},{"name":2020,"color":2021},2907,"[Performance improvement opportunity]: remove disabled-dependent classes on links created with `UButton`","2025-01-13T22:45:37Z","https://github.com/nuxt/ui/issues/2907",0.69573057,{"description":2059,"labels":2060,"number":2061,"owner":1988,"repository":2008,"state":2032,"title":2062,"updated_at":2063,"url":2064,"score":2065},"Hi there and thanks so much for your work!\r\n\r\nRecently I've upgraded `nuxt 3.12.4` to `nuxt 3.13.2`, `@nuxt/ui@2.18.4` to `@nuxt/ui@2.18.6`, `@tailwindcss/forms@0.5.7, @tailwindcss/typography@0.5.14` to `@tailwindcss/forms@0.5.9, @tailwindcss/typography@0.5.15`. Here are some observations.\r\n\r\nIcons stop working on initial site loading (and 50/50% on next loads):\r\n\r\n1. Navigate to webpage (generated by `npm run generate`, incognito mode, no cache): no icons.\r\n2. Refresh page: sometimes there are icons, sometimes not, sometimes only half of them.\r\n\r\n```\r\nThe above happens whether one upgrades to `@nuxt/ui@2.18.6`,`@tailwindcss/forms@0.5.9, @tailwindcss/typography@0.5.15` within `nuxt 3.12.4`.\r\n\r\nOr\r\n\r\nOne upgrades to `nuxt 3.13.2` and `@nuxt/ui@2.18.6`.\r\n\r\nOr \r\n\r\nSometimes when one simply upgrades to `nuxt 3.13.2`.\r\n```\r\n\r\nWhat fixes an issue:\r\n\r\n1. Downgrading to `nuxt 3.12.4` with `@nuxt/ui@2.18.4` and `@tailwindcss/forms@0.5.7 @tailwindcss/typography@0.5.14` fixes an issue.\r\n3. Installiing collections locally (in my case `@iconify-json/bxl, @iconify-json/heroicons, @iconify-json/heroicons-solid`) and adding:\r\n```ruby\r\nicon: {\r\nclientBundle: {\r\n scan: true,\r\n sizeLimitKb: 256, }, },\r\n```\r\n\r\nHowewer one question still bothers me. Same `nuxt/ui`. `3.12.4` without the above settings works like a charm, but when updating the above deps barely loads icons. Just changing deps and the necessity of the the above arises. But why?\r\n\r\n`3.12.4` and `nuxt/ui@2.18.6` with `@tailwindcss/forms@0.5.9, @tailwindcss/typography@0.5.15` together result in the issue without the above settings (with `nuxt/ui@2.18.4` and `@tailwindcss/forms@0.5.7, @tailwindcss/typography@0.5.14` everything works fine).\r\n\r\n`3.13.2` with `nuxt/ui@2.18.6` result in the issue as well (keeping tailwind deps old). And sometimes just upgrading to `3.13.2` results in the issue.\r\n\r\nWith the minimal amount of site payload (one page - 2-3 icons) - `3.13.2` works fine without the above changes. When full project is in place - icons without the above changes stop working. I'm talking about `npm run generate` with `ssr:true`. `npm run build` works in every case.\r\n\r\nCan someone elaborate?\r\n\r\nAlso you can easily reproduce this behavior (node `v20.17.0)`. \r\n1. repo: https://github.com/gAlleb/nuxt-om\r\n2. `npm install`.\r\n3. Run `npm run generate` - all icons work fine.\r\n\r\n4. Upgrade `npm install @nuxt/ui@2.18.6 @tailwindcss/forms@0.5.9 @tailwindcss/typography@0.5.15`.\r\n\r\nor\r\n\r\n5. Upgrade `npx nuxi upgrade` and `npm install @nuxt/ui@2.18.6`\r\n\r\n6. Navigate to webpage (generated by `npm run generate`, incognito mode, no cache).\r\n\r\n7. Icons won't load without `clientBundle` setting and adding `local collections`.\r\n\r\nThanks!\r\n\r\n\r\n\r\n\r\n\r\n",[],259,"Icons aren't loaded (@nuxt-ui)","2024-11-20T16:54:06Z","https://github.com/nuxt/icon/issues/259",0.6968649,{"description":2067,"labels":2068,"number":1987,"owner":1988,"repository":1999,"state":2032,"title":2072,"updated_at":2073,"url":2074,"score":1994},"\n\n",[2069],{"name":2070,"color":2071},"bug","ff281a","[Home] Responsive hero","2023-02-15T12:30:55Z","https://github.com/nuxt/nuxt.com/issues/750",{"description":2076,"labels":2077,"number":2081,"owner":1988,"repository":2023,"state":2032,"title":2082,"updated_at":2083,"url":2084,"score":2085},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.10.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@9.6.7\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.10, @nuxt/eslint@0.7.2, @nuxtjs/i18n@9.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\nNone\n\n### Description\n\nThank you very much for providing such a great component library. I'm trying to use it in my personal project.\n\nThe following is the relevant code:\n```ts\nconst columns = computed(() => defaultColumns.filter(column => selectedColumns.value.includes(column.accessorKey)))\n```\n```vue\n\u003CUTable\n :columns=\"columns\"\n :data=\"data\"\n/>\n```\n\n---\nI checked the latest documentation, and the examples of UTable regarding column display control seem to have no effect, such as: https://ui3.nuxt.dev/components/table#with-column-visibility.\n\n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2078,2080],{"name":2070,"color":2079},"d73a4a",{"name":2020,"color":2021},2874,"The update of the columns property will not trigger an update of the UTable component","2025-01-25T13:12:40Z","https://github.com/nuxt/ui/issues/2874",0.6993084,["Reactive",2087],{},["Set"],["ShallowReactive",2090],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"ziYwt9tZRIdVtr_zCvdAkxD2F_Zn_k1xUYr6ZG3_IN4":-1},"/nuxt/test-utils/475"]