Improve creation of logpoints and conditional breakpoints
Categories
(DevTools :: Debugger, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: sebo, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: ux-efficiency)
User Story
Sometimes you set a breakpoint but actually wanted to create a logpoint or the other way round. Or you have a logpoint set and investigated the info logged to the console but want more contextual information, so you want to set a breakpoint.
Attachments
(1 file)
|
36.84 KB,
image/png
|
Details |
Breakpoint context menu
There should be a way to turn breakpoints into logpoints and the other way round.
Currently, you have to remove the breakpoint and set the logpoint. And if you had a condition set, you need to type in the condition again.
Therefore, it would be a bit easier if there was an option to switch between the two types.
The obvious way to do that would be a new context menu entry. Though there might also be some keyboard shortcut for that.
|
||
Comment 1•11 months ago
|
||
Note that there is three types of breakpoints: regular pause breakpoint, conditional breakpoint and log breakpoint.
You are meaning to switch between log and condition breakpoints.
Because switching from regular conditional/pause breakpoint and log point is easy, you only need to add the log string.
The other way around from conditional/log point to regular pause breakpoint is also easy, you can strip the condition/log string and the breakpoint will become a regular pause breakpoint.
This feature request collides a bit with the current feature set implemented in the UI, where you can set both conditional and log breakpoints.
When you are using both, the condition will condition the log point, you will no longer pause.
I imagine that supporting the existing setup and a switch would involve yet another context menu, while the context menu is already quite complex.
|
|
||
Comment 2•11 months ago
|
||
|
||
Comment 3•8 months ago
|
||
After discussing with the team, it would be nice to have a single "breakpoint" and then have a UI to "Edit breakpoint" which allows to add a condition, make it a logpoint instead etc... That would be a bit closer to what chrome is doing, and would be less confusing than having several types of breakpoints potentially on the same line.
This might also be useful if we get an additional type of breakpoints for the tracer.
Description
•