`\r\n\r\nchunk-SOI3BFCQ.js?v=091eb3ff:1759 [Vue warn]: Hydration attribute mismatch on \u003Cimg src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632814\" alt> \r\n - rendered on server: src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632814\"\r\n - expected on client: src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632813\"\r\n Note: this mismatch is check-only. The DOM will not be rectified in production due to performance overhead.\r\n You should fix the source of the mismatch. \r\n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \r\n at \u003CAnonymous key=\"/search\" vnode= {__v_isVNode: true, __v_skip: true, type: {…}, props: {…}, key: null, …} route= {fullPath: '/search?title=dd', hash: '', query: {…}, name: 'search', path: '/search', …} ... > \r\n at \u003CBaseTransition onAfterLeave= [ƒ] mode=\"out-in\" appear=false ... > \r\n at \u003CTransition onAfterLeave= [ƒ] name=\"page\" mode=\"out-in\" > \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CDefault ref=Ref\u003C undefined > > \r\n at \u003CLayoutLoader key=\"default\" layoutProps= {ref: RefImpl} name=\"default\" > \r\n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"default\" name=\"default\" ... > \r\n at \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\n\r\n### Reproduction\r\n\r\nchunk-SOI3BFCQ.js?v=091eb3ff:1759 [Vue warn]: Hydration attribute mismatch on \u003Cimg src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632814\" alt> \r\n - rendered on server: src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632814\"\r\n - expected on client: src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632813\"\r\n Note: this mismatch is check-only. The DOM will not be rectified in production due to performance overhead.\r\n You should fix the source of the mismatch. \r\n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \r\n at \u003CAnonymous key=\"/search\" vnode= {__v_isVNode: true, __v_skip: true, type: {…}, props: {…}, key: null, …} route= {fullPath: '/search?title=dd', hash: '', query: {…}, name: 'search', path: '/search', …} ... > \r\n at \u003CBaseTransition onAfterLeave= [ƒ] mode=\"out-in\" appear=false ... > \r\n at \u003CTransition onAfterLeave= [ƒ] name=\"page\" mode=\"out-in\" > \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CDefault ref=Ref\u003C undefined > > \r\n at \u003CLayoutLoader key=\"default\" layoutProps= {ref: RefImpl} name=\"default\" > \r\n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"default\" name=\"default\" ... > \r\n at \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\n\r\n### Describe the bug\r\n\r\nchunk-SOI3BFCQ.js?v=091eb3ff:1759 [Vue warn]: Hydration attribute mismatch on \u003Cimg src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632814\" alt> \r\n - rendered on server: src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632814\"\r\n - expected on client: src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632813\"\r\n Note: this mismatch is check-only. The DOM will not be rectified in production due to performance overhead.\r\n You should fix the source of the mismatch. \r\n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \r\n at \u003CAnonymous key=\"/search\" vnode= {__v_isVNode: true, __v_skip: true, type: {…}, props: {…}, key: null, …} route= {fullPath: '/search?title=dd', hash: '', query: {…}, name: 'search', path: '/search', …} ... > \r\n at \u003CBaseTransition onAfterLeave= [ƒ] mode=\"out-in\" appear=false ... > \r\n at \u003CTransition onAfterLeave= [ƒ] name=\"page\" mode=\"out-in\" > \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CDefault ref=Ref\u003C undefined > > \r\n at \u003CLayoutLoader key=\"default\" layoutProps= {ref: RefImpl} name=\"default\" > \r\n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"default\" name=\"default\" ... > \r\n at \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\n\r\n### Additional context\r\n\r\nchunk-SOI3BFCQ.js?v=091eb3ff:1759 [Vue warn]: Hydration attribute mismatch on \u003Cimg src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632814\" alt> \r\n - rendered on server: src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632814\"\r\n - expected on client: src=\"/_nuxt/assets/image/searchBg.jpg?t=1707570632813\"\r\n Note: this mismatch is check-only. The DOM will not be rectified in production due to performance overhead.\r\n You should fix the source of the mismatch. \r\n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \r\n at \u003CAnonymous key=\"/search\" vnode= {__v_isVNode: true, __v_skip: true, type: {…}, props: {…}, key: null, …} route= {fullPath: '/search?title=dd', hash: '', query: {…}, name: 'search', path: '/search', …} ... > \r\n at \u003CBaseTransition onAfterLeave= [ƒ] mode=\"out-in\" appear=false ... > \r\n at \u003CTransition onAfterLeave= [ƒ] name=\"page\" mode=\"out-in\" > \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CDefault ref=Ref\u003C undefined > > \r\n at \u003CLayoutLoader key=\"default\" layoutProps= {ref: RefImpl} name=\"default\" > \r\n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"default\" name=\"default\" ... > \r\n at \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\n\r\n### Logs\r\n\r\n_No response_",[3099,3102,3103,3106],{"name":3100,"color":3101},"3.x","29bc7f",{"name":3019,"color":3020},{"name":3104,"color":3105},"needs reproduction","FBCA04",{"name":3107,"color":3108},"⛔️ can be closed","484893",25730,"Image error bug","2024-03-29T20:49:34Z","https://github.com/nuxt/nuxt/issues/25730",0.73884714,{"description":3115,"labels":3116,"number":3120,"owner":3022,"repository":3022,"state":3067,"title":3121,"updated_at":3122,"url":3123,"score":3124},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v20.11.1\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: yarn@4.2.1\r\n- Builder: -\r\n- User Config: devtools, experimental\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://github.com/timhn-bm/nuxt-client-fallback-errors\r\n\r\nI've added 2 pages\r\n- `/works` - not using the `ErrorBoundary` wrapper: it behaves correctly :heavy_check_mark: \r\n- `/bugs` - using the `ErrorBoundary` wrapper: it reproduces the bug :red_circle: \n\n### Describe the bug\n\nWhen building a wrapper around `NuxtClientFallback` and using it is used in multiple places on one page, given that one wrapped component throws an error, then all instances of `NuxtClientFallback` will display the `fallback` slot **only after hydration**\r\n\r\n\r\n\n\n### Additional context\n\nI want to build a wrapper component around `NuxtClientFallback`.\r\n\r\nThe wrapper - let's call it `ErrorBoundary` - can look like this in its simplest form\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003CNuxtClientFallback :keep-fallback=\"true\">\r\n \u003Cslot> \u003C/slot>\r\n\r\n \u003Ctemplate #fallback>\r\n \u003Cdiv style=\"background: red; color: white; padding: 10px\">\r\n \u003Cslot name=\"error\"> \u003C/slot>\r\n \u003C/div>\r\n \u003C/template>\r\n \u003C/NuxtClientFallback>\r\n\u003C/template>\r\n```\r\n\r\nIf I create a page with the following template: `A` `B` and `C` are wrapped by my custom `ErrorBoundary`.\r\n\r\nIf `A` throws an error -> after hydration, then the error slot will also by displayed for `B` and `C`\r\n\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv >\r\n \u003CErrorBoundary>\r\n \u003CA /> --> only A will throw an error \r\n \u003Ctemplate #error> an error occurred in A \u003C/template>\r\n \u003C/ErrorBoundary>\r\n\r\n \u003CErrorBoundary>\r\n \u003CB />\r\n \u003Ctemplate #error> an error occurred in B \u003C/template>\r\n \u003C/ErrorBoundary>\r\n\r\n \u003CErrorBoundary>\r\n \u003CC />\r\n \u003Ctemplate #error>\r\n \u003Cdiv>an error occurred in C\u003C/div>\r\n \u003C/template>\r\n \u003C/ErrorBoundary>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nThe very weird this, is that if I use directly `NuxtClientFallback` instead of my wrapper `ErrorBoundary`, then everything behaves as expected.\r\n\r\nThanks for your help in advance !\n\n### Logs\n\n_No response_",[3117,3118],{"name":3076,"color":3088},{"name":3119,"color":3105},"🔨 p3-minor",28344,"NuxtClientFallback renders fallback for all components if one failed, after hydration","2024-12-20T10:13:47Z","https://github.com/nuxt/nuxt/issues/28344",0.750063,{"description":3126,"labels":3127,"number":3134,"owner":3022,"repository":3022,"state":3067,"title":3135,"updated_at":3136,"url":3137,"score":3138},"### Versions\r\n\r\n- nuxt: 2.15.3\r\n- node: v12.19.0\r\n- css-loader: 4.3.0\r\n\r\n### Steps to reproduce\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"class-a\">\u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cstyle lang=\"scss\" scoped>\r\n.class-a {\r\n background-image: url(\"http://abc.xyz.jpg?foo/bar\");\r\n}\r\n\u003C/style>\r\n```\r\n\r\nAnd the run `npm run build`\r\n\r\n### What is Expected?\r\n```\r\n.class-a {\r\n `background-image: url(http://abc.xyz.jpg/?foo%2Fbar);\r\n}\r\n```\r\n\r\n### What is actually happening?\r\nThe backgroundImage url params has been encoded to be `background-image: url(http://abc.xyz.jpg/?foo%2Fbar=)`,.\r\nthere is a `=` at the end of the url, that make the image resource is invalid.\r\n\r\n### Addition\r\nIf run `npm run dev`, that's all right.\r\n",[3128,3130,3131],{"name":3064,"color":3129},"ffffff",{"name":3019,"color":3020},{"name":3132,"color":3133},"2.x","d4c5f9",9064,"BackgroundImage url will be added a '=' at the end of url params when run build","2023-01-22T15:38:48Z","https://github.com/nuxt/nuxt/issues/9064",0.7568709,{"description":3140,"labels":3141,"number":3148,"owner":3022,"repository":3066,"state":3067,"title":3149,"updated_at":3150,"url":3151,"score":3152},"### Environment\n\nNA\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n\"3.0.0-alpha.9\",\n\n### Reproduction\n\nthe UAccordion component triggers a semantic HTML error for each \"dropdown / accordion\" that there is in it.\n\n# 3 dropdowns:\n\n\n\n\n\n\n\n----\n\n# duplicate the accordion (so now 6 dropdowns)\n\n\n\n\n\n\n\n\n\n\n### Description\n\nthe UAccordion component triggers a semantic HTML error for each \"dropdown / accordion\" that there is in it.\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3142,3143,3144,3146,3147],{"name":3076,"color":3088},{"name":3058,"color":3059},{"name":3145,"color":3129},"triage",{"name":3061,"color":3062},{"name":3064,"color":3062},2782,"UAccordion semantic HTML errors","2025-06-18T09:05:31Z","https://github.com/nuxt/ui/issues/2782",0.7596303,["Reactive",3154],{},["Set"],["ShallowReactive",3157],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fuOOUPrfbWuJaSdhp8aGzb4lLvYbbx4m1N7k0FRqqxRI":-1},"/nuxt/ui/4048"]