diff --git a/content/en/api-reference/browser-compatibility/chrome-flags.mdx b/content/en/api-reference/browser-compatibility/chrome-flags.mdx index f397ac0..7f6747b 100644 --- a/content/en/api-reference/browser-compatibility/chrome-flags.mdx +++ b/content/en/api-reference/browser-compatibility/chrome-flags.mdx @@ -179,3 +179,6 @@ Visit via `about://flags/` | Usage | `"%LOCALAPPDATA%\Google\Chrome SxS\Application\chrome.exe" --allow-third-party-modules` | + +## Additional Resources +- [Chromium: services/webnn/webnn_switches.h](https://source.chromium.org/chromium/chromium/src/+/main:services/webnn/webnn_switches.h;l=30) diff --git a/content/en/learn/get-started/debug.mdx b/content/en/learn/get-started/debug.mdx index 617768a..2eac4af 100644 --- a/content/en/learn/get-started/debug.mdx +++ b/content/en/learn/get-started/debug.mdx @@ -12,7 +12,7 @@ import NvidiaIcon from '../../../../app/_components/icons/ihv/nvidia.jsx' 1. Follow the [WebNN Installation Guide](installation) to enable WebNN API and switch to Windows ML / ONNX Runtime backend 2. Put the ONNX Runtime dynamic link librares into a folder under `C:\Program Files\`, e.g. `C:\Program Files\ONNXRuntime` -3. Launch your Chrome or Edge browser with switch [--webnn-ort-library-path-for-testing](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-library-path-for-testing) +3. Launch your Chrome or Edge browser with switch [`--webnn-ort-library-path-for-testing`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-library-path-for-testing)
```shell @@ -32,7 +32,7 @@ If you are running WebNN on AMD, Intel, Nvidia, or Qualcomm devices and need to 1. Follow the [WebNN Installation Guide](installation) to enable WebNN API and switch to Windows ML / ONNX Runtime backend 2. Put the ONNX Runtime and Execution Provider dynamic link librares into a folder under `C:\Program Files\`, e.g. `C:\Program Files\ONNXRuntime-EP` -3. Launch your Chrome or Edge browser with switch [--webnn-ort-ep-library-path-for-testing](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-ep-library-path-for-testing) +3. Launch your Chrome or Edge browser with switch [`--webnn-ort-ep-library-path-for-testing`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-ep-library-path-for-testing) ### Execution Provider Mapping Table for Independent Hardware Vendors @@ -97,7 +97,7 @@ TBD ## Use Custom Build of GPU or NPU Drivers -If you are testing with custom or internal GPU or NPU drivers, add the [--allow-third-party-modules](../../api-reference/browser-compatibility/chrome-flags#--allow-third-party-modules) switch when launching the browser. +If you are testing with custom or internal GPU or NPU drivers, add the [`--allow-third-party-modules`](../../api-reference/browser-compatibility/chrome-flags#--allow-third-party-modules) switch when launching the browser.
```shell @@ -113,7 +113,7 @@ If you are testing with custom or internal GPU or NPU drivers, add the [--allow- ## Debug Sandbox Issues -In some cases, you may need to debug WebNN by disabling Chromium's security sandbox using the [--disable-gpu-sandbox](../../api-reference/browser-compatibility/chrome-flags#--disable-gpu-sandbox) switch. +In some cases, you may need to debug WebNN by disabling Chromium's security sandbox using the [`--disable-gpu-sandbox`](../../api-reference/browser-compatibility/chrome-flags#--disable-gpu-sandbox) switch.
```shell @@ -129,7 +129,7 @@ In some cases, you may need to debug WebNN by disabling Chromium's security sand ## Inspect the Verbose Logging -You can configure the logging severity level of ONNX Runtime using the switch [--webnn-ort-logging-level](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-logging-level). Other available severity levels include "INFO", "WARNING", "ERROR" (default), and "FATAL". +You can configure the logging severity level of ONNX Runtime using the switch [`--webnn-ort-logging-level`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-logging-level). Other available severity levels include "INFO", "WARNING", "ERROR" (default), and "FATAL".
```shell @@ -143,6 +143,17 @@ You can configure the logging severity level of ONNX Runtime using the switch [- ```
+## Additional Debug Options + +Additional WebNN switches are available: + +- [`--webnn-ort-graph-optimization-level`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-graph-optimization-level) +- [`--webnn-ort-enable-profiling`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-enable-profiling) +- [`--webnn-ort-dump-model`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-dump-model) +- [`--webnn-tflite-dump-model`](../../api-reference/browser-compatibility/chrome-flags#--webnn-tflite-dump-model) + + ## Additional Resources -- [WebNN Flags and Switches in Chromium](../../api-reference/browser-compatibility/chrome-flags) \ No newline at end of file +- [WebNN Flags and Switches in Chromium](../../api-reference/browser-compatibility/chrome-flags) +- [Chromium: services/webnn/webnn_switches.h](https://source.chromium.org/chromium/chromium/src/+/main:services/webnn/webnn_switches.h;l=30) \ No newline at end of file diff --git a/content/en/learn/get-started/installation.mdx b/content/en/learn/get-started/installation.mdx index e1951c5..72335cb 100644 --- a/content/en/learn/get-started/installation.mdx +++ b/content/en/learn/get-started/installation.mdx @@ -88,4 +88,8 @@ Provider 1: ### Search for `ONNX Runtime backend for WebNN` and change it to `Disabled` ### Search for `DirectML backend for WebNN` and change it to `Disabled` ### Relaunch browser - \ No newline at end of file + + +## Debug + +If you are a developer, visit the [debug page](./debug) for information about WebNN debugging options. \ No newline at end of file diff --git a/content/zh/api-reference/browser-compatibility/chrome-flags.mdx b/content/zh/api-reference/browser-compatibility/chrome-flags.mdx index f397ac0..9e68501 100644 --- a/content/zh/api-reference/browser-compatibility/chrome-flags.mdx +++ b/content/zh/api-reference/browser-compatibility/chrome-flags.mdx @@ -179,3 +179,6 @@ Visit via `about://flags/` | Usage | `"%LOCALAPPDATA%\Google\Chrome SxS\Application\chrome.exe" --allow-third-party-modules` |
+ +## Additional Resources +- [Chromium: services/webnn/webnn_switches.h](https://source.chromium.org/chromium/chromium/src/+/main:services/webnn/webnn_switches.h;l=30) \ No newline at end of file diff --git a/content/zh/learn/get-started/debug.mdx b/content/zh/learn/get-started/debug.mdx index 617768a..2eac4af 100644 --- a/content/zh/learn/get-started/debug.mdx +++ b/content/zh/learn/get-started/debug.mdx @@ -12,7 +12,7 @@ import NvidiaIcon from '../../../../app/_components/icons/ihv/nvidia.jsx' 1. Follow the [WebNN Installation Guide](installation) to enable WebNN API and switch to Windows ML / ONNX Runtime backend 2. Put the ONNX Runtime dynamic link librares into a folder under `C:\Program Files\`, e.g. `C:\Program Files\ONNXRuntime` -3. Launch your Chrome or Edge browser with switch [--webnn-ort-library-path-for-testing](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-library-path-for-testing) +3. Launch your Chrome or Edge browser with switch [`--webnn-ort-library-path-for-testing`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-library-path-for-testing)
```shell @@ -32,7 +32,7 @@ If you are running WebNN on AMD, Intel, Nvidia, or Qualcomm devices and need to 1. Follow the [WebNN Installation Guide](installation) to enable WebNN API and switch to Windows ML / ONNX Runtime backend 2. Put the ONNX Runtime and Execution Provider dynamic link librares into a folder under `C:\Program Files\`, e.g. `C:\Program Files\ONNXRuntime-EP` -3. Launch your Chrome or Edge browser with switch [--webnn-ort-ep-library-path-for-testing](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-ep-library-path-for-testing) +3. Launch your Chrome or Edge browser with switch [`--webnn-ort-ep-library-path-for-testing`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-ep-library-path-for-testing) ### Execution Provider Mapping Table for Independent Hardware Vendors @@ -97,7 +97,7 @@ TBD ## Use Custom Build of GPU or NPU Drivers -If you are testing with custom or internal GPU or NPU drivers, add the [--allow-third-party-modules](../../api-reference/browser-compatibility/chrome-flags#--allow-third-party-modules) switch when launching the browser. +If you are testing with custom or internal GPU or NPU drivers, add the [`--allow-third-party-modules`](../../api-reference/browser-compatibility/chrome-flags#--allow-third-party-modules) switch when launching the browser.
```shell @@ -113,7 +113,7 @@ If you are testing with custom or internal GPU or NPU drivers, add the [--allow- ## Debug Sandbox Issues -In some cases, you may need to debug WebNN by disabling Chromium's security sandbox using the [--disable-gpu-sandbox](../../api-reference/browser-compatibility/chrome-flags#--disable-gpu-sandbox) switch. +In some cases, you may need to debug WebNN by disabling Chromium's security sandbox using the [`--disable-gpu-sandbox`](../../api-reference/browser-compatibility/chrome-flags#--disable-gpu-sandbox) switch.
```shell @@ -129,7 +129,7 @@ In some cases, you may need to debug WebNN by disabling Chromium's security sand ## Inspect the Verbose Logging -You can configure the logging severity level of ONNX Runtime using the switch [--webnn-ort-logging-level](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-logging-level). Other available severity levels include "INFO", "WARNING", "ERROR" (default), and "FATAL". +You can configure the logging severity level of ONNX Runtime using the switch [`--webnn-ort-logging-level`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-logging-level). Other available severity levels include "INFO", "WARNING", "ERROR" (default), and "FATAL".
```shell @@ -143,6 +143,17 @@ You can configure the logging severity level of ONNX Runtime using the switch [- ```
+## Additional Debug Options + +Additional WebNN switches are available: + +- [`--webnn-ort-graph-optimization-level`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-graph-optimization-level) +- [`--webnn-ort-enable-profiling`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-enable-profiling) +- [`--webnn-ort-dump-model`](../../api-reference/browser-compatibility/chrome-flags#--webnn-ort-dump-model) +- [`--webnn-tflite-dump-model`](../../api-reference/browser-compatibility/chrome-flags#--webnn-tflite-dump-model) + + ## Additional Resources -- [WebNN Flags and Switches in Chromium](../../api-reference/browser-compatibility/chrome-flags) \ No newline at end of file +- [WebNN Flags and Switches in Chromium](../../api-reference/browser-compatibility/chrome-flags) +- [Chromium: services/webnn/webnn_switches.h](https://source.chromium.org/chromium/chromium/src/+/main:services/webnn/webnn_switches.h;l=30) \ No newline at end of file diff --git a/content/zh/learn/get-started/installation.mdx b/content/zh/learn/get-started/installation.mdx index e1951c5..72335cb 100644 --- a/content/zh/learn/get-started/installation.mdx +++ b/content/zh/learn/get-started/installation.mdx @@ -88,4 +88,8 @@ Provider 1: ### Search for `ONNX Runtime backend for WebNN` and change it to `Disabled` ### Search for `DirectML backend for WebNN` and change it to `Disabled` ### Relaunch browser - \ No newline at end of file + + +## Debug + +If you are a developer, visit the [debug page](./debug) for information about WebNN debugging options. \ No newline at end of file