Bug: canvas becomes non-interactive after switching to Test mode > navigating > leaving Test mode
Have tested on Chrome and Brave . I can interact with the editor UI (sidebars etc ) but just nothing in the canvas . I tried to debug it a bit . What I have attached are two screenshots of the iframe . The one with the data -mode = "design " attribute on the body is a screenshot from a freshly refreshed page of the editor where the canvas was interactive . The other screenshot is of the same thing but after going into Test mode > navigating to a page > leaving Test mode . At a guess it looks like it 's not detecting that I 've left Test mode ? This is a known limitation of the editor . Once you navigate away from the page /component that you ’ve selected , the editor and the canvas become “out of sync ” . We ’ve tried to address this by opening all links in new tabs , but some actions are still able to navigate the canvas away from the selected component /page . We ’re still undecided on how to handle this atm The best way to deal with it when you ’re working on a component /page is probably to open the preview mode 🤷♂️ this wasn 't always the case though right ? I swear I used to use Test mode a bunch to jump between pages , then jump out of Test mode and edit those pages . Now though , if I use Test mode , navigate away , then leave Test mode even selecting a Page or Component from the sidebar doesn 't do anything anymore . So Test mode atm is only working for a single page , and navigating to any other page breaks the editor and requires a reload . perhaps you could just confirm then that this experience is expected : https://www.loom.com/share/7f977ebff7b74fdbb6b31f5c26e6772f?sid=653bc131-e7b1-45c3-8601-2eaa142a2638 Essentially Test mode breaks interactions with the canvas and navigating to pages /components via the sidebar I believe it has always been working like this yes . We 've had other users reporting the same here : - https://discord.com/channels/972416966683926538/1195770542087749652/1197094608455352401 - https://discord.com/channels/972416966683926538/1115805480623800450/1151775733409128458 Test mode only works for a single page /component at a time yes . And if you want to work on another page /component you will need to select it from the left menu . Obviously we want to improve this and make it more clear when /if the canvas is out of sync with the editor , and potentially load the new component automatically so highlighting just works . I 'll make sure it 's on our roadmap to investigate the best solution here 👍 👍1I just hit whatever internal limit 'triggers ' this behavior . Until tonight , it has always managed to stay in sync , even when I figured it would lose its way . So , no . The behavior of falling out of sync is not consistent , but it is once you pass some internal threshold . Note : I 'm not complaining . . . .just trying to help with future updates . I 've found that the simplest workaround is to have a 'dev button ' on each page that allows you to trigger the same functionality as an 'On load ' event . That way you can load each page and populate data or whatever , without falling out of sync . Once the page is 'done /perfect , ' just remove the dev button .
.jpeg/public)