Closed
Bug 690569
Opened 13 years ago
Closed 13 years ago
Evaluating declarations in Scratchpad makes it oddly unresponsive
Categories
(DevTools :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 679467
People
(Reporter: jimb, Unassigned)
Details
If I open a ScratchPad, type the text var enterCount = "hi"; and hit Ctrl-l, I get no feedback at all. If I then type, on the next line, enterCount and hit Ctrl-l, I again get no feedback. If I then type, on the next line, enterCount = 0 and hit Ctrl-l, I again get no feedback. Even if something evaluates to 'undefined', Ctrl-l should at least do something to indicate that it did it. "/* ok */" would be fine. :) This may or may not be relevant to the resolution of this bug, but it'd also be nice to have some indication of what ScratchPad actually tried to parse when I just hit Ctrl-l without selecting the text first. (Is it always that present line? Can't I type multi-line things and evaluate them, or must I select first?)
Comment 1•13 years ago
|
||
We're doing developer tool prioritization, filter on 'brontozaur' to ignore the spam.
Priority: -- → P3
Comment 2•13 years ago
|
||
Falsy values are currently not displayed by Scratchpad when code is evaluated. We need to fix this. Thanks for your report!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•