Closed
Bug 947655
Opened 11 years ago
Closed 9 years ago
Inspector doesn't show tooltip after refresh, but intercepts click events where tooltip should be
Categories
(DevTools :: Inspector, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: david.crawford, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36
Steps to reproduce:
1. Open a page with a short body
2. Open the inspector (you should see a tooltip indicating the body element)
3. Refresh the page (the box reappears around the body, but the tooltip doesn't)
4. Right click where the tooltip used to be.
Actual results:
The pointer is a text pointer rather than a click pointer, the page doesn't react to clicks or right-clicks in that spot. It's like there's an invisible tooltip there.
Expected results:
Either the tooltip should display, or the click events should still go to the page. I spent an hour trying to find out where the click events were going before I realized everything worked fine when the inspector was closed.
Reporter | ||
Updated•11 years ago
|
Component: Untriaged → Developer Tools: Inspector
This seems to be working for inspector clicks in the same area. It would be best to include a screenshot if you are still having this issue.
Tested in Firefox 41.0a2 (2015-07-25).
(please close)
Flags: needinfo?(david.crawford)
The tooltip seems to be working when I followed the above steps. I did it on windows 10 64-bit processor.
Tested on Nightly firefox-46.0a2.
Comment 3•9 years ago
|
||
This bug is more than 2 years old, and the inspector has changed quite a lot in the meantime.
I think that by tooltip, the reporter meant the node info bubble that appears when a node is highlighted in the page.
The highlight now doesn't stay visible on the page all the time as it used to, so the steps described can't be used anymore to reproduce the issue.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Comment 5•9 years ago
|
||
(In reply to kshitija from comment #4)
> Does that mean issue is solved?
It means this bug is invalid now, not a problem anymore.
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•