'Step in' exits function
Categories
(DevTools :: Debugger, defect, P1)
Tracking
(firefox-esr60 unaffected, firefox-esr68 wontfix, firefox68 wontfix, firefox69 wontfix, firefox70 fixed)
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | wontfix |
firefox68 | --- | wontfix |
firefox69 | --- | wontfix |
firefox70 | --- | fixed |
People
(Reporter: Oriol, Assigned: jlast)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [debugger-mvp])
Attachments
(1 file)
- Run this code in the console:
(function(){ debugger; var a = 1; var b = 2; })();
- The debugger pauses at
debugger;
- Step in
Expected: the debugger pauses at var a = 1;
Result: the debugger pauses at })();
Regression window: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b7ae64d5ac774ce9054e8aa3431ecd992594447b&tochange=0ab76cc4232f56936e1a2609823f0c13272ca449
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Comment 3•6 years ago
|
||
bugherder |
Comment 4•6 years ago
|
||
Is this something we should consider uplifting to Beta for Fx69 or can it ride to release with Fx70?
Updated•6 years ago
|
Updated•6 years ago
|
Comment 6•6 years ago
|
||
(In reply to Jason Laster [:jlast] from comment #5)
I don't think it is important enough.
Is it? It sounds like a very disturbing breakage to have around breakpoints. One which can make developer quite unhappy regarding our tools quality. I thought that breakpoint correctness was a top level goal for the debugger?
Now, it is very surprising for me to see how long it took to get a report about this breakage, which may be the one reason to not consider this as important.
Assignee | ||
Comment 7•6 years ago
|
||
Harald and I discussed this last week and it is a difficult call.
This bug makes it impossible to step through console evaluated code. On the other hand, this fix is somewhat risky and could affect much more common use cases.
Given that, I am hesitant to uplift the changeset and have a small window to address any unforseen issues before they go out to release.
Comment 8•6 years ago
|
||
A(In reply to Jason Laster [:jlast] from comment #7)
This bug makes it impossible to step through console evaluated code. On the other hand, this fix is somewhat risky and could affect much more common use cases.
Ah sorry. I was mislead by the bug title. I missed that it was only when the code we step through is from a console evaluation. I thought it was more generic than that.
I now better understand your call! It sounds sensible to me as well.
Updated•3 years ago
|
Description
•