Confirmed users
125
edits
DevTools/OperationInstrument: Difference between revisions
Jump to navigation
Jump to search
m
→2. Telling the DevTools Frontend About the New Markers: bold
(→2. Telling the DevTools Frontend About the New Markers: describe properties) |
|||
| Line 56: | Line 56: | ||
To get your new markers displayed in the performance tool's UI, edit the configuration data in '''<code>browser/devtools/shared/timeline/global.js</code>'''. | To get your new markers displayed in the performance tool's UI, edit the configuration data in '''<code>browser/devtools/shared/timeline/global.js</code>'''. | ||
Add a property to the <code>TIMELINE_BLUEPRINT</code> object. The property key should be the <code>const char *</code> literal that you added in step 1 ("Parse HTML" in our example). The new property should be an object with the following properties: | Add a property to the '''<code>TIMELINE_BLUEPRINT</code>''' object. The property key should be the <code>const char *</code> literal that you added in step 1 ("Parse HTML" in our example). The new property should be an object with the following properties: | ||
* <code>group</code>: 0, 1, or 2. Controls which line the markers are rendered on in the trace events summary along the top of the performance tool. When in doubt, just use 0 and ask your reviewer. | * <code>group</code>: 0, 1, or 2. Controls which line the markers are rendered on in the trace events summary along the top of the performance tool. When in doubt, just use 0 and ask your reviewer. | ||