David_S

Thanks for the reply. Looking into it more just now, I see what was causing my confusion. I just re-tried editing some buttons that I had added while developing... removed the link, and re-added to the page using SS's chooser... and it inserted the relative link, but kept the demo URL when hovering over those buttons (in the editor). However, when loading the actual site with its public URL via a private window, those links DO show the correct URL. I was getting worried when I saw the links on SS's backend weren't updating, when that's not what I should've been looking at! Thanks again for helping me figure that out 🙂

Hi folks. When I create relative links (e.g. to files or other pages), Squarespace is insisting on using the built-in domain (which I had set to SITE-preview for dev purposes). It is still doing this despite setting the primary domain to be the actual purchased domain, so the 'development' domain is still showing when you hover over links etc, which isn't great. I've checked domain settings and the bought domain is the 'primary' domain, so why isn't SS using this when creating links across the site? How can I make this happen? I've gone into some of the links and manually added the real domain to the front of relative links, but I'd like to know if there's an easier/better way to 'fix' it?

Yep, just have to hope a future version of Safari treats this use case better, I guess 🤷‍♂️ -- thanks Paul.

Hi Paul! Here's my test page: https://uphere.media/background-video-test Edit: Works in Chrome, small glitch on repeat in Safari here (v 12.1.2)

I’m using a paid Vimeo plan for hosting videos and see the flicker in Safari on macOS ... but not on iOS. Which is slightly infuriating. Fingers crossed for an update to Safari fixing it, I’ll look into version numbers when back at a desk.

Did you get any further with this? I've noticed this happening in Safari, but not Chrome. I'm wondering why the "flicker" in Safari... and can't find anyone else talking about it! It seems there's nothing that can be done? Any other thoughts? (anyone?)

Just wanted to say a big THANK YOU for this workaround. It's super annoying this isn't supported natively yet, but also super appreciated to have solutions like this posted, which when I try them, just work! You've made me very happy, thank you! 🙇‍♂️