Open
Bug 1107763
Opened 10 years ago
Updated 2 years ago
Add a "pause on coerce to NaN" option to the debugger's options dropdown
Categories
(DevTools :: Debugger, enhancement, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: fitzgen, Unassigned)
References
(Depends on 1 open bug, Blocks 2 open bugs)
Details
Add the ability to pause on coercion to NaN.
|
||
Updated•10 years ago
|
Depends on: dbg-control
|
Reporter | |
Comment 1•9 years ago
|
||
No time for this at the moment.
Assignee: nfitzgerald → nobody
Status: ASSIGNED → NEW
|
||
Updated•7 years ago
|
Priority: -- → P3
|
||
Updated•6 years ago
|
Product: Firefox → DevTools
|
||
Updated•5 years ago
|
Type: defect → enhancement
|
|
||
Updated•5 years ago
|
Blocks: dbg-control
No longer depends on: dbg-control
|
||
Comment 2•5 years ago
|
||
My recommendation is to expose Coercion pausing in the Event BP panel, from which we can then iterate to expose it properly – I would love to hear more thoughts though.
Blocks: dbg-event-bps
|
||
Comment 3•5 years ago
|
||
My main question in this is whether this is something SpiderMonkey can expose for us easily. Since it would be a broad flag, probably on Debugger, I could see it causing deoptimization for any math operation, and any builtin that can produce NaN. I'd want their thoughts on whether that is something that could be problematic.
|
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•