@SteveB you need to strip out everthing on that page to just Contol Centre and a Foundry button and test it. Test in Preview and then in Safari. If Ok, then add in every other stack one by one and test each time.
Otherwise you will go round and round for ever. Also I have had some projects become unstable and the only cure was to delete and rebuild from a fresh blank page.
It’s weird that it’s working for you, have you tried the one above too? i sent the same to Tav and as I understand it, he also saw the problem. He expanded it a bit too.
Anyway, here is a video of what is happening here. I show how the link doesn’t open in a new window, then after I remove balls it does. I’m not for one moment saying the issue is balls, as removing the video child from SP has the same effect: The link opens on a new window. And I suspect if I hunted around I’d find other stacks that make the problem happen/not happen.
I’m not looking to apportion blame just get to the bottom of it if it has a bottom to get to.
Assuming it’s not just me being thick (possible) there is something going on here, I can’t establish if it’s happening only on my machine or a wider issue. Then, if a wider issue I can’t establish what is causing it. For that, I need the input of the devs.
I’ve said this before, it can’t be done. That is the point. It seems a be a mixture of stacks on the page that is causing it, but it’s not uniform, the mixture is random as far as I can tell. The two I’ve isolated it down to is Paddy Balls and SP with a Video Child, if I tried I suspect I can do the same with other stacks. The one single constant though is the Foundry theme, which is why I’ve now bought it to Adam, to see if he wants to and can shed any light. he can’t though as he doesn’t have the stacks needed to replicate the problem.
I still don’t even know if you’re seeing the issue as I’m seeing it in the video.
I don’t need a fix to this, I’ve found a workaround, I’m just trying to help first establish if this is a wider issue and then help nail it down if it can be. I do completely understand that this is probably “just one of those things”, I just thought it might be worth seeing if there was something else going on, that maybe might be worth resolving. Who knows, it might be something simple that might lead on to something else. But we’ll never know if we keep going round in circles.
Maybe it should just be parked now, I have my fix, if some other poor buggers hits it or a related issue, it’ll be their problem.