Closed
Bug 1906320
Opened 3 months ago
Closed 3 months ago
Make dirtyFrame's purpose more obvious in browser/base/content/test/performance/head.js
Categories
(Firefox :: General, task, P3)
Firefox
General
Tracking
()
RESOLVED
FIXED
129 Branch
| Tracking | Status | |
|---|---|---|
| firefox129 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
Details
Attachments
(1 file)
A few of us had a conversation about our reflow tests in Matrix, and we had to dig a lot of context out of the ol' memory-hole to remember why dirtyFrame was being used so often. We should make that more explicit in the code for future readers.
|
Assignee | |
Updated•3 months ago
|
Assignee: nobody → mconley
|
|
Assignee | |
Comment 1•3 months ago
|
||
Hopefully this comment and marker will make it so that we don't have to
chase any ghosts in rr in the future to understand what dirtyFrame is
doing!
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/388b934b83bb
Try to make dirtyFrame's purpose more clear, and add a profiler marker. r=emilio
|
||
Comment 3•3 months ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 months ago
status-firefox129:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 129 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•