New issue
Advanced search Search tips

Issue 704290 link

Starred by 3 users
Status: Archived
Owner:
einbinder@chromium.org
Closed: Oct 31
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Inactive DOM Breakpoints shouldn't be visible in the Elements panel

Reported by kdzwinel@gmail.com, Mar 22 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3047.0 Safari/537.36

Steps to reproduce the problem:
1. Open DevTools
2. In the Elements panel right-click on a node
3. Choose "Break on.." -> "attribute change"
4. Go to the Sources panel
5. Find just created breakpoint under "DOM Breakpoints" and disable it (check off the checkbox)
6. Go back to the Elements panel

What is the expected behavior?
Blue dot next to the node is still visible.

What went wrong?
IMO blue dot next to the node shouldn't be shown, or should change color (like JavaScript breakpoints do), when breakpoint is deactivated. 

Note that when breakpoint is deactivated it doesn't show up in the node's context menu under "Break on.." -> "attribute change".

Did this work before? No 

Chrome version: 59.0.3047.0  Channel: dev
OS Version: OS X 10.12.3
Flash Version: 

Removing breakpoint completely works as expected.
blue_dot_sml.mov
8.2 MB Download

Comment 1 by ranjitkan@chromium.org, Mar 27 2017

Labels: Needs-Triage-M59

Comment 2 by jmukthavaram@chromium.org, Mar 30 2017

Labels: -Needs-Triage-M59 M-59
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Mac 10.12.4,Windows 7 & Ubuntu 14.04 using chrome reported version -59.0.3047.0 ,stable-57.0.2987.133, Canary-59.0.3056.0  as per comment#0.
Observed blue dot is still visible in 'Elements' tab even after disabling 'DOM breakpoints' of Dev tools.
Observed the same issue from M46 and no blue dot visible for the earlier builds of M46.Hence marking it as Untriaged.
Could anybody from dev team please look into this issue.
Thank you.
704290.mp4
2.2 MB View Download

Comment 3 by allada@chromium.org, Apr 6 2017

Owner: einbinder@chromium.org
Status: Assigned (was: Untriaged)
Joel, can you take a look into this. Thanks!

Comment 4 by dgozman@chromium.org, Oct 31

Status: Archived (was: Assigned)
Bulk closing low-priority issues with no activity. Please re-file and refer to the closed issue if it's essential to fix.
►

Sign in to add a comment