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

Issue 628418 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Devtools elements tab's Event Listeners section ignores listeners from extension contexts

Reported by co...@streak.com, Jul 14 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce the problem:
1. Have at least one extension installed (like Adblock Plus) and go to a page where its content script runs.
2. Right-click and inspect an element.
3. Look at the Event Listeners tab on the right.
4. If the page top context doesn't already have event listeners on the element, add some through the console (`$0.addEventListener('foo', ()=>{});`). They correctly show up in the Event Listeners section.
5. If the page extension doesn't already have event listeners on the element, then switch the console to the extension's context and then add some through the console.

What is the expected behavior?
Either all of the event listeners for the element across all contexts should show up, or all of the event listeners for the currently-selected context should show up.

What went wrong?
Only the event listeners from the "top" context show up.

I've attached a screenshot showing me go through this in devtools. (Yes, I clicked the little refresh button in the Event Listeners section at the end.)

Did this work before? Yes 

Chrome version: 51.0.2704.106  Channel: stable
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 22.0 r0

Possibly related to https://bugs.chromium.org/p/chromium/issues/detail?id=628412 . I think both issues were introduced in the same Chrome version.
 
Screen Shot 2016-07-14 at 4.00.26 PM.png
98.5 KB View Download

Comment 1 by alph@chromium.org, Jul 15 2016

Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Status: Archived (was: Assigned)
Bulk DevTools triage, closing low priority issues with no action plan.

Sign in to add a comment