Closed Bug 948893 Opened 11 years ago Closed 11 years ago

Hovering certain bounds in a HTML source while paused in the debugger can sometimes show a variable inspection popup

Categories

(DevTools :: Debugger, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 29

People

(Reporter: vporof, Assigned: vporof)

Details

Attachments

(2 files)

      No description provided.
Attached file test.html
STR:
1. Open debugger on test.html
2. Click me
3. Hover trololol
Assignee: nobody → vporof
Status: NEW → ASSIGNED
Attachment #8345831 - Flags: review?(past)
Summary: Hovering whitespace in a HTML source while paused in the debugger can sometimes show a variable inspection popup → Hovering certain bounds in a HTML source while paused in the debugger can sometimes show a variable inspection popup
Comment on attachment 8345831 [details] [diff] [review]
dbg-vview-popup-html.patch

Review of attachment 8345831 [details] [diff] [review]:
-----------------------------------------------------------------

::: browser/devtools/debugger/test/browser_dbg_variables-view-popup-09.js
@@ +25,5 @@
> +      ok(false, "The variable inspection popup shouldn't have been opened.");
> +    });
> +
> +    reopenVarPopup(panel, { line: 18, ch: 10 });
> +    yield waitForTime(1000);

I assume for this to work we need 1000 >> EDITOR_VARIABLE_HOVER_DELAY, so maybe we should enforce it before someone decides to change the latter value causing oranges? Not that I'm confident we will avoid them anyway in our slow build machines :-)
Attachment #8345831 - Flags: review?(past) → review+
(In reply to Panos Astithas [:past] from comment #4)
> 
> I assume for this to work we need 1000 >> EDITOR_VARIABLE_HOVER_DELAY, so
> maybe we should enforce it before someone decides to change the latter value
> causing oranges? Not that I'm confident we will avoid them anyway in our
> slow build machines :-)

It's not necessarily related to that. Even if I remove the yield and there was, in fact, a problem with the debugger, the test would fail immediately.

However, the thing is, we want to make sure a popup never opens (in the reverse scenario), and we don't have an event for that :) We could add one, but maybe emitting an event whenever the mouse moves and an identifier isn't found might slow down things? I don't know.

We can't possible have time-dependant oranges here, except when the Parser becomes dumb again for whatever reason, in which case the test will fail immediately anyway. So I'm not too worried.
https://hg.mozilla.org/mozilla-central/rev/fe3e00a67749
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 29
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: