Modern browser automation relies heavily on Chrome DevTools Protocol, but Safari lacks native CDP support. This article explores how to build automation from scratch by solving three core challenges: React’s internal state tracking, Shadow DOM encapsulation, and Content Security Policy restrictions. By combining DOM-level workarounds, recursive traversal techniques, and multi-layer execution fallbacks—including AppleScript—the author demonstrates a robust, framework-agnostic approach to browser automation outside the Chromium ecosystem.