Closed
Bug 1669266
Opened 4 years ago
Closed 4 years ago
Make DOMEvent not a tracing marker
Categories
(Core :: Gecko Profiler, task, P2)
Core
Gecko Profiler
Tracking
()
RESOLVED
FIXED
83 Branch
| Tracking | Status | |
|---|---|---|
| firefox83 | --- | fixed |
People
(Reporter: gregtatum, Assigned: gregtatum)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
For markers 2.0, we need the DOMEvent to not be a tracing marker in order to properly use the schema. This handles the Gecko-side of the upgrade.
The front-end was handled here: https://github.com/firefox-devtools/profiler/pull/2813
The front-end needs to be deployed before landing this bug.
|
Assignee | |
Comment 1•4 years ago
|
||
This is part of the Markers 2.0 work. This payload proved to be a bit ambiguous
when moving to the new marker schema, so it requires an upgrader.
The test is included as the following commit.
Blocks: 1640999
Pushed by gtatum@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/410bdec8b73e
Upgrade the DOMEvent marker to not be of type "tracing" r=gerald
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox83:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•