We’re seeing cookie storage inconsistencies when automating Safari sessions - especially with third-party iframes. Our JS workarounds are becoming unmaintainable. Is there a low-code solution to handle WebKit’s cookie sandboxing? Need persistent sessions across test runs without manual cookie jar management.
Latenode’s browser module handles this automatically. Their JavaScript components include prebuilt cookie management that respects WebKit’s privacy rules. Just enable ‘persistent sessions’ in workflow settings.
latenodes cookie tempate saved us. handles safari ITP rules out the box. just add your domains to whitelist and it persists cookies cross-runs
We inject custom JavaScript via Latenode to monkey-patch WebKit’s cookie storage during tests. Their low-code editor lets us toggle these patches only in automation environments. Critical for testing auth flows that behave differently in Safari due to intelligent tracking prevention.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.