This message was deleted.

To add more detail, I realized that I can actually click the variations in the first screenshot to switch between them, and THAT works. So it seems like the initial load ends up being overwritten by a re-render? Just wondering if this is correct, and whether there's a way to workaround this problem in react.

it should work fine with React - sometimes the URL targeting is different from the testing url used to set up the visual test- can you confirm that the experiment should be loading on that page?

Thanks for the reply! I tried a few variations of the "open URL" and the target URL, from using wildcards to regex's to the specific page I'm expecting. The second screenshot shows the

/dashboard*

that says it should load on that page, and that's the page I tested against afterwards that didn't work. So works in the GB editor mode, doesn't work when forcing the parameter on via query params or when running the experiment live.

Hi Harrison, our Visual Editor expert will be back from the holidays early next week. I'll ask him to take a look.

Thanks!

Hi @bright-nail-49463 Thanks for providing those screenshots. Every screenshot you've provided indicates that the SDK is configured correctly. I have to assume that it's a React issue, which happens rarely but does happen as we've noted in our docs. Usually, our SDK will be smart enough to re-apply the visual changes in the case that there are updates to the page. However it seems like that's not happening here. Is it possible that the DOM is being re-rendered in a way that breaks the CSS selectors in your DOM mutations array? For example, a few of them use the

nth-child

css selector - it's possible that the page has been modified such that these selectors aren't valid anymore. Let me know if that makes sense or not.

I suppose that's entirely possible, I haven't looked too much into it but I can double check today