commit | 8c5a639cf2679fe41fd1f642175f6e6f4024e9a1 | [log] [tgz] |
---|---|---|
author | Jack Franklin <[email protected]> | Fri Jun 07 10:38:03 2024 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 07 11:07:58 2024 |
tree | 762e274d1963f398f7f0fb70ddbbe15637af95a1 | |
parent | db4a4c48daba098dcbbadc2faf7e8879300c48eb [diff] [blame] |
Add VE Logging notes for `setVeDebugLoggingEnabled` Bug: none Change-Id: I25b407bf0d467521f9f663ab6a671b0b46d1bea2 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5604431 Commit-Queue: Jack Franklin <[email protected]> Reviewed-by: Danil Somsikov <[email protected]> Auto-Submit: Jack Franklin <[email protected]> Commit-Queue: Danil Somsikov <[email protected]>
diff --git a/docs/visual_logging.md b/docs/visual_logging.md index c0f51cd..ab54e54 100644 --- a/docs/visual_logging.md +++ b/docs/visual_logging.md
@@ -196,3 +196,7 @@ **Note:** This will only work if you invoked Chrome with the command line flag `--enable-features=DevToolsVeLogging`. Otherwise you won't see any red lines. + +You can also run `setVeDebugLoggingEnabled(true)` in DevTools on DevTools. This +will cause each VE log to be also logged to the DevTools on DevTools console. +They will also be stored in the global variable `veDebugEventsLog`.