New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 681506 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

FR. Jump to every framework listener when the DOM listener is in the blackbox file

Reported by ovkadu...@gmail.com, Jan 16 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2982.0 Safari/537.36

Steps to reproduce the problem:
Please checkout jsfiddle in here https://jsfiddle.net/ovkadurin/d5r25tpn/ . Also there is animated gif attached.

So DevTools can detect "framework listeners". It's possibile to see them if go to the "Elements panel" -> "Framework listeners" tab.
Then if setting the "Event Listener Breakpoint: Mouse -> Click", then clicking on the Div make Source panel opens a jQuery file at the line jQuery's common listener is set. It's fine.
Then if blackboxing jQuery file and clicking on the Div, then the first listener in the custom code appears. Then if clicking "Resume script execution" the  debugger will go to the next breakpoint (if any). 

My feature request is as follows. 
When the DOM listener is located in the file which is blackboxed, and the engine can recognize framework listeners, then when clicking on the "Resume script execution", debugger should go to the every framework listener (not just to the first one in the "whitelist" file). The list of the framework listeners (if they are not in the blackboxed files) should be the same as in the "Elements panel" -> "Framework listeners" tab.

What is the expected behavior?

What went wrong?
FR 

Did this work before? N/A 

Chrome version: 57.0.2982.0  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0
 
two_framework_listeners.gif
968 KB View Download
Labels: Needs-Triage-M57
Status: Untriaged (was: Unconfirmed)
As this seems to be a feature request, hence marking it as Untriaged.

Thanks..

Comment 3 by caseq@chromium.org, Jan 17 2017

Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by caseq@chromium.org, Jan 17 2017

Components: -Platform>DevTools Platform>DevTools>JavaScript
Labels: -Pri-2 Pri-3
As workaround: you can use "Step out current function" to go to the next event listener from current one.

Comment 6 by ovkadu...@gmail.com, Jan 17 2017

kozyatin...@chromium.org, thanks a lot! 
Labels: -Needs-Triage-M57 M-58
Removed Needs-Triage-M57 as its a Feature request and added appropriate milestone.
Status: Fixed (was: Assigned)
I think this workaround is actually more then just workaround.

Sign in to add a comment