Zooming on traces with only one DOM event is buggy
Categories
(DevTools :: Debugger, enhancement)
Tracking
(firefox130 fixed)
Tracking | Status | |
---|---|---|
firefox130 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
When the trace displays a unique call tree, for example when tracing:
data:text/html,<script>window.onclick = foo; function foo() {}</script>
Zooming will quickly trigger the following exception:
can't access property "length", this.props.getChildren(...) is undefined
And before reaching this exception, the tree may display more than the expected number of elements.
This isn't trivial to spot without enabling the stdout logs of Tracer.js and looking at start and end indexes.
Assignee | ||
Comment 1•4 months ago
|
||
Updated•4 months ago
|
Assignee | ||
Comment 2•4 months ago
|
||
When zooming past the last top trace, i.e. on the last call tree,
we should be using the startIndex of unique top trace and nothing else.
Assignee | ||
Comment 3•4 months ago
|
||
The end index is meant to be exclusing (while the start is inclusive)
Comment 5•4 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/5325ad7cd570
https://hg.mozilla.org/mozilla-central/rev/20fb070ee3ca
https://hg.mozilla.org/mozilla-central/rev/c15579c965d5
Description
•