Closed Bug 825543 Opened 12 years ago Closed 9 years ago

Node info bar still responds to mouse pointer when hidden

Categories

(DevTools :: Inspector, defect, P2)

20 Branch
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: darktrojan, Unassigned)

Details

STR:
* Inspect an element with the inspector panel. Note the position of the node info bar.
* Switch to a different panel. The node info bar disappears, but if you move the mouse to where it was, the cursor changes to an I-beam or you get the tooltip of the bar.
OS: Linux → All
Hardware: x86 → All
Version: unspecified → 20 Branch
Is it still true in a very recent nightly? I thought I fixed that (bug 817705).
Please re-open if you still have the problem.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Yes, I still see this in the latest Nightly.

This seems to be the problem:
http://hg.mozilla.org/mozilla-central/file/a812ef63de87/browser/base/content/highlighter.css#l73
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
I think we should destroy the highlighter, not just hide it.
Priority: -- → P2
I can confirm this is an issue in the latest Aurora, and it can be a really issue if you don't catch on to what's happening. In mt case, the node info element was sitting over something I was trying to test by clicking. It just seemed like the page was buggy until I randomly clicked on the invisible node info element's select dropdown. It became clear this was what was blocking my UI events.

Any chance we can get a fix to this soon? It can make you think there are other issues with your app or Firefox if you don't happen to discover the real source of the issue.
"can be a really *difficult* issue" - I'm tired :/
I believe this will be addressed in the new implementation of the highlighter.
Marking as WONTFIX since the node info bar no longer exists
Status: REOPENED → RESOLVED
Closed: 12 years ago9 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.