Depth is incorrect and DOM events aren't shown when source are ignored
Categories
(DevTools :: Debugger, enhancement)
Tracking
(Not tracked)
People
(Reporter: ochameau, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
When using blackboxing, the tracer can be confusing.
In the console, the depth will be looking weird as it will be the actual depth of frame, without considering that some parent frame were ignored and not displayed.
In the debugger, the depth is ignored visually, but as it is used to display the DOM events, as soon as the top most frame is ignored, the DOM events are no longer shown. It may also introduce some confusions in some case in the tree when depth ends up connecting and we are not have a depth=0 frame which force to create a new parent element in the tree.
|
Reporter | |
Comment 1•3 months ago
|
||
The depth was incorrect, ultimately leading to miss the top level DOM event being correctly reported to the frontend.
We only report the current DOM Event for frame with detph being reported to zero.
Description
•