From c4365bf2d28452ad7b4139e7c177fd250be2cf2f Mon Sep 17 00:00:00 2001 From: aditya-vithaldas Date: Fri, 10 Jul 2026 21:27:49 +0200 Subject: [PATCH] Document Web Inspector access --- changelog.d/web-inspector-docs.md | 1 + docs/src/app/debugging/page.mdx | 6 ++++++ 2 files changed, 7 insertions(+) create mode 100644 changelog.d/web-inspector-docs.md diff --git a/changelog.d/web-inspector-docs.md b/changelog.d/web-inspector-docs.md new file mode 100644 index 00000000..2910b895 --- /dev/null +++ b/changelog.d/web-inspector-docs.md @@ -0,0 +1 @@ +improvement: **Web Inspector docs**: the debugging guide now explains how macOS WebView apps open the WebKit inspector and points native-rendered UI debugging back to automation snapshots. diff --git a/docs/src/app/debugging/page.mdx b/docs/src/app/debugging/page.mdx index 460f679c..1477beaf 100644 --- a/docs/src/app/debugging/page.mdx +++ b/docs/src/app/debugging/page.mdx @@ -151,6 +151,12 @@ For apps with [web content](/frontend), build with `-Ddebug-overlay=true` to ena native dev -Ddebug-overlay=true ``` +## Web Inspector + +On macOS, apps that declare web content get a WebKit inspector entry in the native View menu. Run the app, focus the WebView window, then choose **View > Toggle Web Inspector** or press ⌥⌘I. Canvas-only apps do not show the item because there is no WebView to inspect. + +The inspector is for the web surface: DOM, console, network, storage, and frontend JavaScript. For native-rendered UI state, use [Automation](/automation) snapshots and widget driving instead. + See also [native doctor](/debugging/doctor) for a full diagnostic tool reference. ## Environment variables