webkit_skill

Overview

This skill provides practical guidance for embedding and controlling web content in SwiftUI apps using WebView and WebPage. It covers loading URLs or HTML, navigation control, JavaScript interop, snapshots/PDF export, and common configuration needs like private browsing and custom user agents.

How this skill works

WebView displays web content in a SwiftUI view while WebPage is an observable controller that manages loading, navigation state, and configuration. You create a WebPage to load URLRequests, HTML strings, or data blobs, observe navigation events for loading and errors, execute JavaScript safely with argument binding, and customize behavior via WebPage.Configuration and WebsiteDataStore options.

When to use it

• Embedding a webpage or HTML content inside a SwiftUI app
• Needing navigation control (back, forward, reload) or loading state
• Executing JavaScript from Swift and receiving results or messages
• Intercepting or cancelling navigation and handling custom URL schemes
• Capturing snapshots, exporting PDFs, or exporting web archives

Best practices

• Use WebPage + WebView(page) when you need navigation, events, or programmatic control
• Always import both SwiftUI and WebKit when using WebPage APIs
• Observe page.currentNavigationEvent for loading indicators and error handling
• Wait for a .finished navigation event before calling callJavaScript to ensure the DOM is ready
• Use WebsiteDataStore.nonPersistent() for private browsing to avoid saving user data
• Pass JavaScript arguments via the arguments: parameter to avoid injection and improve debugging

Example use cases

• A help center screen that loads remote docs and supports back/forward navigation
• An embedded dashboard that calls page JavaScript to update charts and reads results back to Swift
• A privacy-focused view that uses a nonPersistent data store and a custom user agent
• A feature that snapshots a rendered invoice page and exports it as a PDF
• Intercepting navigation to open payment links in an external app or handle custom scheme callbacks