Breakpoint in contentAreaClick not hit in new windows
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
People
(Reporter: Gijs, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
|
||
Updated•10 years ago
|
|
||
Updated•6 years ago
|
|
||
Comment 1•6 years ago
|
||
I was testing this and my BP didn't hit at step #6
@Gijs: do you see the same?
Honza
|
Reporter | |
Comment 2•6 years ago
|
||
(In reply to Jan Honza Odvarko [:Honza] (always need-info? me) from comment #1)
I was testing this and my BP didn't hit at step #6
@Gijs: do you see the same?
Honza
Of course, because this was 4 years ago and now we have e10s, so contentAreaClick isn't called in the parent process anymore, we use ContentClick.jsm or whatever it's called, on the content process.
https://searchfox.org/mozilla-central/source/browser/base/content/browser.js#1491-1495
The same bug probably might still exist in other code that does get hit in the e10s case.
|
|
||
Comment 3•6 years ago
|
||
I was testing this with the following STRs:
- open Firefox + browser debugger
- go to www.mozilla.org
- in the browser debugger, open resource://devtools/client/netmonitor/src/app.js
- set a breakpoint on the first line in bootstrap function (line 33 atm)
- Open DevTools select the Network panel
--> the breakpoint gets hit - open a new window and DevTools + Network panel again
--> the breakpoint does get hit again
I was also checking some others code (including chrome://), but didn't see the problem.
Closing
@Gijs, please reopen if you can repro that!
Honza
Description
•