\r\n\r\n\n\n### Describe the bug\n\nComplete meltdown of nuxt, infinite loop\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2025,2028],{"name":2026,"color":2027},"3.x","29bc7f",{"name":2029,"color":2030},"pending triage","E99695",21818,"Iframes on Self","2023-06-28T09:46:05Z","https://github.com/nuxt/nuxt/issues/21818",0.7787311,{"description":2037,"labels":2038,"number":2040,"owner":1994,"repository":1994,"state":2008,"title":2041,"updated_at":2042,"url":2043,"score":2044},"Hello. I have very important module that I can't setup with Nuxt, please help.\r\n\r\n```html\r\n\u003Cvideo id=\"player\" class=\"video-js\" controls autoplay>\r\n \u003Csource src=\"http://vjs.zencdn.net/v/oceans.mp4\" type=\"video/mp4\">\u003C/source>\r\n\u003C/video>\r\n```\r\n```js\r\nmounted () {\r\n video('player')\r\n }\r\n```\r\nThis works only if I navigate directly on that page or reload it. This doesn't work if I navigate to this page from other pages in my app. \r\n\r\nHow to fix it?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c2117\">#c2117\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2039],{"name":2005,"color":2006},2442,"Video.js doesn't work when route on client","2023-01-18T15:55:18Z","https://github.com/nuxt/nuxt/issues/2442",0.779769,{"description":2046,"labels":2047,"number":2049,"owner":1994,"repository":1994,"state":2008,"title":2050,"updated_at":2051,"url":2052,"score":2053},"As menthiod in https://github.com/nuxt/nuxt.js/issues/1272 I was troubled by the flash\r\n\r\nnow I find that, if I click the link at the top, every thing works ok, but when I click the link at the bottom(scrollbar), this page will first at current page up to top, and then go to another page, then the flash come.\r\n\r\nyou can visit https://www.awesomes.cn/repos/Applications\r\n\r\nThen just click both `react` and `pdf.js`,you will find the flash caused by scrollbar\r\n\r\n\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1401\">#c1401\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2048],{"name":2005,"color":2006},1571,"about the flash","2023-01-18T15:41:58Z","https://github.com/nuxt/nuxt/issues/1571",0.78204197,{"description":2055,"labels":2056,"number":2059,"owner":1994,"repository":1994,"state":2008,"title":2060,"updated_at":2061,"url":2062,"score":2063},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, pages\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt3-iframe-leak\n\n### Describe the bug\n\nIn my `index.vue` page I create an `iframe` element, which is rendering my `iframe.vue` page:\r\n\r\n```vue\r\n// index.vue\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv>This is index page content!\u003C/div>\r\n \u003Ciframe src=\"/iframe\">\u003C/iframe>\r\n\u003C/template>\r\n```\r\n\r\n```vue\r\n// iframe.vue\r\n\r\n\u003Cscript setup>\r\n console.log('Hello World inside iframe!');\r\n\u003C/script>\r\n\r\n\u003Ctemplate>This is iframe content.\u003C/template>\r\n\r\n\u003Cstyle>\r\n* {\r\n color: red;\r\n}\r\n\u003C/style>\r\n```\r\n\r\nThe problem is that both style and script leak from iframe to parent page (`index.vue`).\r\nAll elements are red and I also see message in console log.\r\n\r\nHow to prevent iframe from applying styles and script to parent page?\r\n\r\nHere is a working [example][1] on Stackblitz.\r\n\r\n[![enter image description here][2]][2]\r\n\r\n\r\n [1]: https://stackblitz.com/edit/nuxt3-iframe-leak\r\n [2]: https://i.stack.imgur.com/CNH39.gif\n\n### Additional context\n\nI am trying to create an editor. Heavy work is done in worker and the rendered result I want to send to iframe and set content.\n\n### Logs\n\n_No response_",[2057,2058],{"name":2026,"color":2027},{"name":2029,"color":2030},24689,"IFrame style and script leak to parent page","2024-02-13T08:01:17Z","https://github.com/nuxt/nuxt/issues/24689",0.78317183,{"description":2065,"labels":2066,"number":2068,"owner":1994,"repository":1994,"state":2008,"title":2069,"updated_at":2070,"url":2071,"score":2072},"I've been trying to port my vue.js application to nuxt.js for a few days now and I've got to be honest, I've ran into a lot of problems so far. Problems that never happened when my website was a normal vue.js app.\r\n\r\nSo, right now I've ran into another problem. I'll try to explain.\r\n\r\nWhen I load my website, it loads in a `VideoPlayer` component that I've made my self, the video player works perfectly fine, when I was using it with my normal vue.js app there were no bugs and also the many unit tests I've wrote for the player all pass as well.\r\n\r\nNow this video player that I made, for some reason gets generated twice on page loads. The first time that it generated the video player, it gets put into the DOM (I think) but right after it, it gets replaced with a new video player instance.\r\n\r\nNow the problem is this, when the first video player gets removed, all of the events are still attached and it still tries to load the video. Even though the video player isn't in the DOM anymore, the video still gets played in the background.\r\n\r\nWhat ends up happening is that we end up with two videos playing at the same time, one in background and one from the actual player.\r\n\r\n@manniL and I are very confused about this problem, we've been trying to debug it for a few days but we're getting no where with it.\r\n\r\nI have a feeling that its something to do with how nuxt.js handles the recycling of components. I've done some debugging and saw that the component gets remounted many times, and so does the page component as well. When it gets remounted, I believe it doesn't destroy the video player properly and still leave the `video` element running background + the events.\r\n\r\nNuxt.js shouldn't be creating new instances of the elements on the page, what it should be doing is recycle the elements it already has there. Otherwise you end up with 5 different `video` elements running background, all that have the same video cached in background as well. That's a lot of memory used for no reason.\r\n\r\nThere's no special event that tells me that the DOM is finally done generating and that it won't be generated again so I can't listen for any of the Vue lifecycle, Vue Router or nuxt events to control that either.\r\n\r\n`no-ssr` isn't option either, I've been spending a lot of time trying to implement it using `no-ssr` and that just creates more bugs then it removes.\r\n\r\nThere's a similar issue over here as well, the fix for it was really hacky and its not appropriate solution I believe since older video objects remain in background. https://github.com/nuxt/nuxt.js/issues/2391\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c2707\">#c2707\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2067],{"name":2005,"color":2006},3126,"Very strange problem, do you think you can help?","2023-01-18T16:09:58Z","https://github.com/nuxt/nuxt/issues/3126",0.7833495,{"description":2074,"labels":2075,"number":2079,"owner":1994,"repository":2080,"state":2008,"title":2081,"updated_at":2082,"url":2083,"score":2084},"Users may want to load multiple scripts of the same provider, for example loading two Google Analytics tags. We need to make sure it's properly supported and documented.\r\n\r\nSee https://github.com/nuxt/scripts/issues/48#issuecomment-2163616397",[2076],{"name":2077,"color":2078},"pre-announce","c2e0c6",97,"scripts","Support / document how to use multiple of the same script","2024-07-13T08:35:24Z","https://github.com/nuxt/scripts/issues/97",0.7836088,{"description":2086,"labels":2087,"number":2090,"owner":1994,"repository":1994,"state":2008,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### Version\r\n\r\n[v1.4.0](https://github.com/nuxt/nuxt.js/releases/tag/v1.4.0)\r\n\r\n### Reproduction link\r\n\r\n[nuxt-test.zip](https://github.com/nuxt/nuxt.js/files/1936662/nuxt-test.zip)\r\n\r\n\r\n### Steps to reproduce\r\n\r\nI found a very strange bug\r\nIf I visit the page in the iframe\r\nWhen you refresh again, the server will be stuck\r\nThe installation code is as follows\r\n\r\n```shell\r\ncd nuxt-test\r\nnpm i\r\nnpm run dev\r\n```\r\nHowever, just put the 143 line comment in /page/index.vue and restart it will not be stuck.\r\n\r\n```js\r\n this.addClickTab('/test-4')\r\n```\r\n\r\nHow to solve this flush stuck bug\r\n\r\n\r\n\r\n\r\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c6953\">#c6953\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2088,2089],{"name":2029,"color":2030},{"name":2005,"color":2006},3258,"A refresh bug about nuxt and iframe","2023-01-22T15:30:04Z","https://github.com/nuxt/nuxt/issues/3258",0.78786284,["Reactive",2096],{},["Set"],["ShallowReactive",2099],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"QNOP_IIQfc_ZEDGWrqQmYKqHG9tnd9XF8OW4BZKvvkI":-1},"/nuxt/scripts/339"]