Diagnosing Safari ITP‑Induced Login Loss and Cookie Clearing
Step‑by‑step guide to diagnose and resolve Safari’s Intelligent Tracking Prevention causing unexpected logouts and cookie loss.
Loading…
ReadMeFeed / Community knowledge
Safari
Real questions. Useful conversations. Find the people who know your stack.
Safari
Developer tools · #safari
Bridging the Web-to-App Gap with Safari's Web Share API
Stop building custom share modals. Learn how to use Safari's Web Share API to trigger native system share sheets, improving user conversion and mobile UX.
Safari's JIT Strategy: Balancing JavaScript Speed and Battery Life
Learn how WebKit's multi-tiered JIT compilation and Lazy JIT approach balance JavaScript performance with battery efficiency on iOS.
javascriptVerifying Layout Breakpoints with Safari Responsive Design Mode
Learn how to use Safari's Responsive Design Mode to verify CSS media queries, simulate Apple device viewports, and debug layout breakpoints without physical hardware.
Which Safari version first introduced fetch duplex support, and can we detect it programmatically before concurrent uploads?
Goal Determine how to programmatically detect whether Safari’s Fetch API will support request streaming (duplex: 'half') when issuing multiple concurrent uploads, rather than relying on ad‑hoc try/catch behavior. Constraints and Uncertainty Safari currently throws or falls back when a ReadableStream body is used with duplex: 'half' . No documented navigator
NSURLErrorClientCertificateRejected when only matching client certificate is expired in WebKit
When a TLS server requests a client certificate during mutual authentication, WebKit's NSURLSession presents identities from the Keychain that match the server's trusted CA list. If the only matching certificate has expired, the authentication challenge fails with NSURLErrorClientCertificateRejected (-1205) and no system-provided fallback UI appears to let t
Safari Back-Forward Cache Restores Stale DOM or Network State
When a user navigates away from a page and then returns using the back or forward button, Safari may restore the page from its Back‑Forward Cache (bfcache) instead of issuing a new document load. In some cases the restored DOM or network‑dependent state appears stale, showing values from the earlier visit rather than reflecting updates that should occur on e
WebAuthn Credential Lifecycle and Revocation in Safari
WebAuthn Credential Management Safari implements WebAuthn credentials scoped to the eTLD+1 to enforce least-privilege access, ensuring that credentials remain origin-bound. These keys are stored within the Secure Enclave or iCloud Keychain for multi-device synchronization. Credential Expiration Constraints The WebAuthn specification does not define a native
Safari Intelligent Tracking Prevention: Configuring Third‑Party Storage Access After Interaction Timer Expires
Goal Design a strategy that ensures third‑party services can reliably access cookies and local storage after Safari’s Intelligent Tracking Prevention (ITP) interaction timer has elapsed. Constraints Safari partitions third‑party data until the user performs a qualifying top‑level interaction. The timer’s remaining duration is not exposed via any public JavaS