Update to DevTools enhanced traces documentation #3615
Conversation
| * **Include script sources in .devtools traces**. | ||
| * **Include DOM snapshots in .devtools traces (experimental)**. | ||
|
|
||
| <!-- TODO: replace once new UI is in canary  --> |
There was a problem hiding this comment.
create enhanced-trace-options.png - The Settings panel in DevTools, showing the trace options
|
|
||
| 1. When the snapshot is recorded, click the **Save** button in the **Memory** tool sidebar: | ||
|
|
||
| <!-- TODO: replace with updated UI  --> |
There was a problem hiding this comment.
create exporting-memory-trace.png - Microsoft Edge with DevTools, showing the Memory tool, with the Save button
|
|
||
| <!-- | ||
| * [Save performance traces](https://developer.chrome.com/docs/performance/save-trace/) | ||
| Leah TODO: confirm chrome link |
There was a problem hiding this comment.
confirm 404 chrome link for "Save performance traces" article
[Save performance traces]
( https://developer.chrome.com/docs/performance/save-trace/ )
https://developer.chrome.com/docs/performance/save-trace/ - 404 (Nov. 3 2025)
try to search Chrome docs for expected title of article:
https://developer.chrome.com/s/results?q=Save%20performance%20traces
There was a problem hiding this comment.
I'm not sure when Chrome will publish their documentation, but we can leave this link out for now if it's not live until Stable 143 and re-add it later.
We would like to update our docs by EOW.
|
Learn Build status updates of commit dad87c8: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 4f5d9ed: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 2cedede: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
|
Learn Build status updates of commit 95f259f: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
|
|
||
| 1. In DevTools, open the **Performance** () tool. | ||
|
|
||
| <!-- Leah TODO: get new png of dialog to show annotations and resource content  --> |
There was a problem hiding this comment.
create save-performance-trace-dialog.png w/ **Include annotations" and "Resource content" instead of "Script content" checkbox
|
|
||
| For example, on Windows, in the `/Downloads/` directory, click the **New folder** button, and then create a `/traces/` directory, in which to save the performance trace file: | ||
|
|
||
| <!-- todo: issue: png shows .. in filename; extension shown is .devtools not .gz --> |
There was a problem hiding this comment.
saving-perf-trace.png issues:
- shows .. in file name
- file name extension shown is .devtools not .gz
|
|
||
| Some Performance insights require resource content (such as scripts) for analysis. The contents of extension scripts are not included in the trace file, even when this checkbox is selected. However, the profiling data from extension scripts is still saved in the trace, because extension scripts can impact performance. | ||
|
|
||
| <!-- todo: |
There was a problem hiding this comment.
link to article section about JavaScript scripts
|
|
||
| <!-- todo: | ||
| See also: | ||
| * []() |
There was a problem hiding this comment.
link to article about source maps
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 9de61c7: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
There was a problem hiding this comment.
inspect/update info tooltips in the dialog https://review.learn.microsoft.com/microsoft-edge/devtools/performance/share-performance-traces-images/save-performance-trace-dialog.png
tooltip 1:
what about html & css?
tooltip 2:
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 2b77065: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
Rendered article sections for review:
Share memory traces with more data
/devtools/experimental-features/share-memory-traces.mdShare enhanced performance and memory traces
/devtools/experimental-features/share-traces.mdShare performance traces with more data
/devtools/performance/share-performance-traces.mdBackground
Enhanced performance traces is shipped upstream. There is a new export UI, and it's no longer considered an experiment. The documentation for this file will live under the Performance section.
Enhanced memory traces remain only downstream. We will keep this documentation under the Experimental features section.
Also, we are no longer using the term "enhanced traces" publicly and it will only be used internally. We need to update our documentation to remove this term.
AB#59906695