| commit | 71006b7e49052e8496719e4226d9c18ffbf3ad06 | [log] [tgz] |
|---|---|---|
| author | Benedikt Meurer <[email protected]> | Mon Dec 18 08:05:50 2023 |
| committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Dec 18 08:29:46 2023 |
| tree | 63a7961b3e24d79a58b571c0ef30f81ec9b8cbc1 | |
| parent | c67fdadcd104ba82740a25feed4fec2931b5f6f3 [diff] [blame] |
[docs] Include a note to turn on the feature correctly. Bug: chromium:1467464, b:308095975 Change-Id: I59bf0b7dae5848f0b70ba686bc79669da728fea7 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5129628 Commit-Queue: Benedikt Meurer <[email protected]> Auto-Submit: Benedikt Meurer <[email protected]> Reviewed-by: Danil Somsikov <[email protected]> Commit-Queue: Danil Somsikov <[email protected]>
diff --git a/docs/visual_logging.md b/docs/visual_logging.md index a6ce219..f459d06 100644 --- a/docs/visual_logging.md +++ b/docs/visual_logging.md
@@ -8,6 +8,9 @@ we can improve the product. This includes understanding what users are seeing, what they are interacting with, and how they are using different features. +To turn on the logging, you need to pass `--enable-features=DevToolsVeLogging` +as command line flag to Chrome. + ## General approach We log impressions and interactions for a subtree of the actual DevTools @@ -190,3 +193,6 @@ structure look like. To do that, call `setVeDebuggingEnabled(true)` in DevTools on DevTools. This will add red outline to each visual element and will show the details of logging config for an element and all its ancestors on hover. + +**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.