- Issue created by @shyam_bhatt
- 🇬🇧United Kingdom jessebaker
I threw a couple of console logs in to see if this was a quick fix but sadly, so far as I can see on a cursory glance, it's not immediately obvious why this isn't working. I've described my findings in the attached image in case that allows someone else to pick this up.
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
I wonder if this is related to Safari's/WebKit's aim to reduce tracking (see https://webkit.org/tracking-prevention/ + https://webkit.org/blog/category/privacy/) and is somehow being triggered for XB too, despite the domains clearly being identical 🤔 Maybe because we're using
srcdoc
, that's considered a separate domain?i.e. perhaps setting
<iframe allow=…>
would fix this? 🤔 See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#allow.Specifically,
allow-same-origin
: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#allow-s... - 🇮🇳India soaratul
I tried allow-same-origin and forceFallback, as mentioned here in this sortablejs issue thread here but none worked 😞
- 🇬🇧United Kingdom jessebaker
Sadly I've just confirmed that this issue still exists after the work to move the iFrame interactions into an overlay ( 🌱 [Proposal] A different approach to the iFrame preview interactions Active ) as it is related to the
<IFrameSwapper>
and thesortableJS
implementation inside the iFrame neither of which have been substantially changed.