[v1.1.0] Possible problem in Safari about filament-peek HOT 9 CLOSED

Yes, unfortunately this is part of the issue I was trying to solve in v1.1.1. allowIframePointerEvents will not work with a preview URL because it's trying to inject some CSS into the page. I'll add it to the documentation. A simple solution would be to add some CSS in your preview component:

    <style>
        body.is-preview a { pointer-events: none !important; }
    </style>

from filament-peek.

Hey @lotarbo, thank you for reporting this, I'll try to replicate it on my end tomorrow. I'll let you know if I find a solution.

from filament-peek.

@pboivin thank you. all i found - recommends using postMessage to communicate between windows

from filament-peek.

Hey @lotarbo, I just tagged v1.1.1 with a fix regarding external URLs for previews. When you have some time, can you give this a quick test and let me know if it works for you?

from filament-peek.

@pboivin thank you. Right now, i don't have errors in console)
But preview still doesn't work in safari. Next.js project hosted on Netlify and uses default preview code from docs. And i saw, Safari can't install Next.js cookies in iframe, that's why i have 404 error i think.
And right now i dont understand, this is problem with iframe, nextjs or headers from both servers(

from filament-peek.

Sorry, i think i found, problem only with safari) https://community.prismic.io/t/troubleshooting-previews/5449#previews-not-working-in-safari-14

from filament-peek.

Thanks for looking into this! So, does the solution in the page you shared solve the problem for you? I think I'm not able to replicate because I'm not using cookies to handle previews on my projects.

from filament-peek.

It helps)
But i have small question: in chrome and safari i can interact with preview frame, but in config i have this
'allowIframePointerEvents' => false,, its normal behavior? Because i this option should prevent interaction

from filament-peek.

Thanks @lotarbo

from filament-peek.