Closed
Bug 708643
Opened 13 years ago
Closed 13 years ago
If Firebug is installed, using "Inspect Element" twice results in 2 inspectors, one uncloseable.
Categories
(DevTools :: Inspector, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 13
People
(Reporter: scjody, Unassigned)
References
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_7) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2
Steps to reproduce:
Aurora version 10.0a2
1. Loaded a page
2. Right click -> Inspect Element
3. Right click -> Inspect Element again
4. Exit the inspector using X on the inspector bar.
Actual results:
After step 3, a new inspector appears on top of the old one.
After step 4, the inspector bar disappears but the screen remains greyed out and the inspector box and bubble remains visible. Reloading the page doesn't help. Running Inspector again doesn't help. Visiting another page causes the screen to remain greyed out with the inspector box and bubble.
Expected results:
After step 3, I expect the element to appear in the existing inspector.
After step 4, I expect the inspector to disappear.
I've only been able to reproduce this problem using a confidential internal application. I can visit another page after step 4, and I will attach a screenshot of what that looks like (and another with 2 inspectors.)
Reporter | ||
Comment 1•13 years ago
|
||
Comment 2•13 years ago
|
||
Can you also test the latest nightly? http://nightly.mozilla.org/
Reporter | ||
Comment 3•13 years ago
|
||
(In reply to Tim (fmdeveloper) from comment #2)
> Can you also test the latest nightly? http://nightly.mozilla.org/
Unfortunately I can no longer reproduce this in Aurora (which updated itself) or in the latest nightly. It was difficult to reproduce to begin with so I'm not sure if it's been fixed or if it's just not happening anymore. Feel free to resolve this as WORKSFORME...
Comment 4•13 years ago
|
||
Will close - if you are able to reproduce again please do post back!
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Comment 5•13 years ago
|
||
I am experiencing this exact problem on an internal page that I am working on. I am using the 10.0 release for Windows.
Comment 6•13 years ago
|
||
Here is a little more information and a test page where I can reproduce this every time.
Test Page: http://webpages.charter.net/jhargett/firefox_insp_test.html
Steps:
1. Right click on the INPUT element with the label "Name".
2. Click "Inspect Element" in the context menu.
3. While the Inspector is still open and has the screen "dimmed", right click on the SELECT element with the label "Select".
4. Click the "Inspect Element" option in the context menu.
Instead of moving the bubble to the SELECT element, it opens a new Inspector window on top of the old one (this is noticeable because the screen gets even dimmer.) It can't find the SELECT element so it goes in to Inspector mode where it puts a bubble over whatever element you mouse over. If you close that inspector, the original one stays open with no way to close it. The only solution at this point is to close the tab and start over.
Comment 7•13 years ago
|
||
Paul, I can reproduce this on nightly, can you take a look please?
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WORKSFORME → ---
Comment 8•13 years ago
|
||
I must be missing something. I can't reproduce. I can't right click on the SELECT element (there's no contextual menu for this element).
Comment 9•13 years ago
|
||
Maybe it is an issue with a different OS? I am on WinXP PRO SP3. I am using FF 10.0. Here is a screencast of it happening on my computer:
http://webpages.charter.net/jhargett/firefox_bug.mp4
Comment 10•13 years ago
|
||
I can't trigger this on win7(aurora), but can trigger on osx 10 (nightly)
Comment 11•13 years ago
|
||
Apparently, Firebug needs to be installed to reproduce this bug.
Comment 12•13 years ago
|
||
jonmhargett, do you have Firebug installed?
Comment 13•13 years ago
|
||
Yes. I will retest with it disabled.
Comment 14•13 years ago
|
||
That was it. I disabled firebug and now the context menu is not available when I right click on a SELECT element. This problem exists with Firebug 1.9.1. So, what is the solution: should Firebug fix this or should you guys make it so that SELECT elements are clickable and the inspector switches to that element?
Updated•13 years ago
|
Summary: Using "Inspect Element" twice results in 2 inspectors, one uncloseable. → If Firefox bug is installed, using "Inspect Element" twice results in 2 inspectors, one uncloseable.
Updated•13 years ago
|
Summary: If Firefox bug is installed, using "Inspect Element" twice results in 2 inspectors, one uncloseable. → If Firebug is installed, using "Inspect Element" twice results in 2 inspectors, one uncloseable.
Comment 15•13 years ago
|
||
Looks fixed in Firebug 1.10.
Comment 16•13 years ago
|
||
It's not "fixed" in Firebug 1.10, it's just that the right-click-on-form feature is broken in 1.10.
The problem is that Firebug allows right-click on forms, and this behavior is not supported by the builin inspector yet: we get a call to openInspectorUI(this.target) where target is null. We don't correctly test this
This patch fix this test. I opened bug 724546 to support right click on forms.
Updated•13 years ago
|
Attachment #594706 -
Flags: review?(dcamp)
Updated•13 years ago
|
Attachment #594706 -
Flags: review?(dcamp) → review+
Updated•13 years ago
|
Whiteboard: [land-in-fx-team]
Comment 17•13 years ago
|
||
This should be landed in Beta and Aurora too.
Comment 18•13 years ago
|
||
Whiteboard: [land-in-fx-team] → [fixed-in-fx-team]
Comment 19•13 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 13
Comment 21•13 years ago
|
||
For what it's worth, this is also an issue on Fedora 14, and I assume, other Linux distributions as well. I would have had a hard time figuring out that it was related to having Firebug installed, so good work, guys.
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•