Event listeners tab does not display list of event listeners
Reported by
edh...@gmail.com,
Mar 13 2017
|
||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36
Steps to reproduce the problem:
1. Open Chrome Dev Tools
2. Open elements tab and open the Event Listeners subtab
3. Select the body html element (or any other element for that matter).
What is the expected behavior?
A list of all event listeners attached to the body (or any ) should be shown.
What went wrong?
The list is empty even when the getEventListeners method returns the correct list:
> getEventListeners(document.body)
Object {click: Array(1), keydown: Array(1), mouseover: Array(1), mouseout: Array(1), dragend: Array(1)}
Did this work before? N/A
Chrome version: 57.0.2987.98 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
It worked previously but I am not sure since which version it does not work.
It works on most websites so I assume it is related to the application in which I am currently working.
,
Mar 15 2017
,
Mar 15 2017
Unable to reproduce this issue on Windows-10 using chrome latest stable M57-57.0.2987.98, Tried multiple times by navigating to different webpages, observed the event listeners list the items as expected. Since there is no consistent repro available for this issue requesting some one from dev team to look in to it. Thanks!
,
Mar 17 2017
Can you include a link to page where you can repro this issue (even if it's inconsistent)? Thanks.
,
Mar 22 2017
edhzsz@ Could you please respond for the comment #4?
,
Apr 5 2017
I have the same problem. It was working like ~2 days before, I think chrome got updated. OS: Windows 10 Chrome: Version 57.0.2987.133 You can try facebook or anyother site, it doesn't matter. The event listeners tab is empty.
,
Apr 5 2017
I am going to guess it's a thrown exception in javascript causing this. Can you please provide us with a stack trace within devtools if this is the case. Next time this occurs can you please do the following steps: 1) close other open tabs 2) open new tab to "chrome://inspect" 3) click "Other" (on the left) 4) click "inspect" on the one listed (there should only be 1 if no other devtools are open) 5) (in the newly opened devtools) open console and see if there are any stack traces. If there are, please post the details of what they are here. 6) (If possible) try and get it to throw a new exception while this new window is opened. Try clicking different elements, open other panels, exc... And hopefully it'll throw again and give a full stacktrace to post here. However, keep in mind this may not be what's happening so there may be no stacktraces making the previous steps useless. Thanks.
,
Apr 10 2017
I can't repro it on M57, we need your help in narrowing it down. Could you confirm that facebook.com, body tag selected, 'ancestors' bit checked is empty? What about the html node itself?
,
Apr 10 2017
Hmm... it seems that the issue appears random. Sometime the event listener tab is ok, sometimes the tab is empty. And it doesn't matter what web page is.
Yes, the 'ancestors' bit is checked. It doesn't matter if the body tag or html tag is selected, the listeners tab is empty sometimes.
@allada
I made the steps, there is more than 1 devtool for me (all of them are something like "devtools-frontend.appspo…", the whole name is not shown). Some of them are trowing errors (just by opening them, I didn't need to click somewhere else):
Main._createAppUI: 43.8ms
inspector.js:8510 Main._showAppUI: 38.4ms
inspector.js:8511 Main._initializeTarget: 20.0ms
3inspector.js:919 TypeError: Cannot read property 'script' of null TypeError: Cannot read property 'script' of null
at new SDK.EventListener (chrome-devtools://devtools/bundled/inspector.js:4783:541)
at SDK.RemoteObjectImpl.createEventListener (chrome-devtools://devtools/bundled/inspector.js:4948:46)
at Array.map (native)
at SDK.RemoteObjectImpl.mycallback (chrome-devtools://devtools/bundled/inspector.js:4947:18)
at callback (chrome-devtools://devtools/bundled/inspector.js:3117:148)
at Protocol.InspectorBackend._AgentPrototype.dispatchResponse (chrome-devtools://devtools/bundled/inspector.js:3124:10)
at SDK.Target._onMessage (chrome-devtools://devtools/bundled/inspector.js:3081:56)
at SDK.MainConnection._dispatchMessage (chrome-devtools://devtools/bundled/inspector.js:3257:41)
at Common.Object.dispatchEventToListeners (chrome-devtools://devtools/bundled/inspector.js:395:23)
at innerDispatch (chrome-devtools://devtools/bundled/inspector.js:919:98)
innerDispatch @ inspector.js:919
Hope it helps you guys. Can help with more info if you tell me what you need.
,
Apr 13 2017
@dgozman: do you think your recent change might have fixed it?
,
Apr 13 2017
Alexey, let's fix this specific place with null-check.
,
Apr 29 2017
I'm also having the same problems: Linux Mint 18.1 64-bit Chrome version: Version 58.0.3029.81 (64-bit) On 2 separate machines, but both have the same Os's and Chrome.
,
May 2 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/81ccbcd9c5b6de950869d165794b7072a6ee7769 commit 81ccbcd9c5b6de950869d165794b7072a6ee7769 Author: dgozman <dgozman@chromium.org> Date: Tue May 02 23:33:21 2017 [DevTools] Check location for null when creating EventListener BUG= 700876 Review-Url: https://codereview.chromium.org/2854853004 Cr-Commit-Position: refs/heads/master@{#468814} [modify] https://crrev.com/81ccbcd9c5b6de950869d165794b7072a6ee7769/third_party/WebKit/Source/devtools/front_end/sdk/DOMDebuggerModel.js
,
May 2 2017
,
Jul 21 2017
hi guys this is not working, still the same issue as reported above some times it shows the events some times id does not also it does not show all the events I am on Version 59.0.3071.115 (Official Build) (64-bit)
,
Jul 28 2017
The same issue here, empty Event Listeners: Version 59.0.3071.109 (Developer Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit) Get help with Chromium |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by woxxom@gmail.com
, Mar 13 2017