The latest articles on DEV Community by Luca Dorigo (@ldorigo). https://dev.to/ldorigo https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1544231%2F3fe2fec4-73cb-4484-b556-05aaf97688c6.jpeg https://dev.to/ldorigo en Luca Dorigo Wed, 29 May 2024 13:30:44 +0000 https://dev.to/ldorigo/state-is-being-shared-across-iframes-56a9 https://dev.to/ldorigo/state-is-being-shared-across-iframes-56a9 <p>We have a next.js app that we normally run by embedding it in an iframe on a third-party website. It uses react and react-query for state management. For a specific usecase, we wanted to run two instances of our app on the same website, and noticed very weird behavior: the state of the two apps is getting jumbled together, and state changes in one iframe <em>sometimes</em> (not always) result in a state change in the other iframe. I wish I could give more details on when/how it happens, but I'm pretty confused by the issue and haven't been able to create a minimal reproducible example. Hopefully someone has an idea to help me troubleshoot?</p> webdev nextjs react javascript