New issue
Advanced search Search tips

Issue 670697 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 637364
Owner: ----
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Conditional breakpoints cannot be accessed from the Breakpoints panel

Project Member Reported by chowse@chromium.org, Dec 2 2016

Issue description

Chrome Version: 54.0.2840.98

Steps to reproduce:
(1) Open https://developers.google.com/ (or any page with some Javascript)
(2) Switch to the Sources tab (or use Ctrl+P) and open a Javascript file.
(3) Add a breakpoint to any line of the file.
(4) Right click on the breakpoint and click 'Edit breakpoint...'
(5) Add a conditional expression and hit Enter
(6) Open the Breakpoints panel in the debugger (the list of all set breakpoints)
(7) Find the breakpoint you just set in the list
(8) Right-click on the breakpoint

Expected result:
(1) An 'Edit breakpoint...' command should be available to view/change the condition.
(2) There should be some indication the breakpoint has a condition attached to it.

Actual result:
(1) There are only options to remove the breakpoint.
(2) There is nothing to indicate a breakpoint is conditional.


There are a couple of ways to address this:
(1a) From the Breakpoints panel, "Edit breakpoint..." could take you to the breakpoint in the code and open the condition panel there.
(1b) The condition panel could be made a popup (e.g. like the color picker) instead of an inline panel. Then it could be opened from both the text editor and the breakpoint panel.
(2a) The checkboxes beside breakpoint could adopt the same colors used to indicate their type (e.g. blue for default breakpoints, orange for conditional).
(2b) The checkboxes could be replaced with debug markers and adopt the same styling as their text editor counterparts (e.g. dimmed if disabled, orange if conditional, etc.)

 

Comment 1 by l...@chromium.org, Dec 2 2016

Mergedinto: 637364
Status: Duplicate (was: Untriaged)
Thank you for the report.  It looks like there is a duplicate ticket with a different name.  I'll forward your description into the other bug.

Sign in to add a comment