Closed Bug 633196 Opened 13 years ago Closed 13 years ago

Object details don't open in the Web Console, when trying a second time

Categories

(DevTools :: General, defect)

All
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: 326374, Assigned: msucan)

Details

(Whiteboard: [patchclean:0210])

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0b11) Gecko/20100101 Firefox/4.0b11
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b11) Gecko/20100101 Firefox/4.0b11

When clicking on an object a window appears

Reproducible: Always

Steps to Reproduce:
1. Open the web console
2. Enter "window" on the command line (or the name of any JS object)
3. The web console responds with "[object Window]"
4. Click that line
5. A window appears - close it
6. Click the same line
Actual Results:  
Nothing happens.

Expected Results:  
The window should reappear with the object details should appear.
WFM on 

Mozilla/5.0 (X11; Linux i686; rv:2.0b12pre) Gecko/20110210 Firefox/4.0b12pre

Try creating a new profile see if that works for you 
http://support.mozilla.com/en-US/kb/Managing%20profiles
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Summary: Object details don't open in the Error Console, when trying a second time → Object details don't open in the Web Console, when trying a second time
Same problem in a new profile. It seems like the bug only occurs when you close the window using the OS close button (not the close button at the bottom of the window), so step 5 needs to be modified.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Well, this is another story then. This is clearly an OS integration issue with Linux. Guys?
Status: UNCONFIRMED → NEW
Ever confirmed: true
sounds likely. We don't have a close button in the title bar on object inspectors in other platforms.
Low priority in my opinion
(In reply to comment #2)
> Same problem in a new profile. It seems like the bug only occurs when you close
> the window using the OS close button (not the close button at the bottom of the
> window), so step 5 needs to be modified.

What linux distro and what theme are you using? My ubuntu Maverick does not have a close button on the pop-up window, so, this is WFM.
David, I can repro this with an Ubuntu 10.04 (32bit)
I'm using Ubuntu 10.10 (maveric).
The close button doesn't appear when turning off all visual effects.
(In reply to comment #8)
> I'm using Ubuntu 10.10 (maveric).
> The close button doesn't appear when turning off all visual effects.

Wow. this is probably a graphics bug. Good find. gonna kick it over there for evaluation.

Make sure to turn on visual effects in appearance.
Component: Developer Tools → Graphics
Product: Firefox → Core
QA Contact: developer.tools → thebes
Hardware: x86 → All
Version: unspecified → Trunk
well - it may be a widget bug. hmm.
yeah, I'm leaning towards widgets.
Component: Graphics → Widget
QA Contact: thebes → general
mihai convinced me that we need to fix this in devtools code.
Component: Widget → Developer Tools
Product: Core → Firefox
QA Contact: general → developer.tools
(In reply to comment #12)
> mihai convinced me that we need to fix this in devtools code.

How is that possible? Compviz puts a close button on the panel. Whatever that does seems to be out of our scope. There are surely other panels affected by this - wouldn't it be better to have it fixed in widgets or elsewhere?
Proposed fix, as discussed with Robert on IRC. We are now not going to care if the window manager shows a Close button or not, in fact we ask for it to show, and we remove our Close button. This is technically a better solution on our side since window managers can always provide users with the ability to close a panel in other ways as well (eg. keyboard shortcuts).
Assignee: nobody → mihai.sucan
Status: NEW → ASSIGNED
Attachment #511448 - Flags: feedback?(rcampbell)
Whiteboard: [patchclean:0210]
(In reply to comment #13)
> (In reply to comment #12)
> > mihai convinced me that we need to fix this in devtools code.
> 
> How is that possible? Compviz puts a close button on the panel. Whatever that
> does seems to be out of our scope. There are surely other panels affected by
> this - wouldn't it be better to have it fixed in widgets or elsewhere?

While you are correct, it is a problem in Widgets, but it's also a problem in our code. We should not rely solely on the use of our Close button for things to work as we want. We have to make sure that when the property panel is closed (no matter how), our code handles the situation properly.

Also, why doesn't the Network Panel suffer the same problem as the Object Inspector? It is because the implementation there relies on the popuphidden event - not on our own Close button. What I propose is simply that we do the same for the Object Inspector.
he's pretty convincing, no?
(In reply to comment #15)
> Also, why doesn't the Network Panel suffer the same problem as the Object
> Inspector? It is because the implementation there relies on the popuphidden
> event - not on our own Close button. What I propose is simply that we do the
> same for the Object Inspector.

I assumed they both had the same problem. Carry on.;)
Comment on attachment 511448 [details] [diff] [review]
[checked-in] proposed fix

acceptable!
Attachment #511448 - Flags: feedback?(rcampbell) → feedback+
Comment on attachment 511448 [details] [diff] [review]
[checked-in] proposed fix

Thanks for the feedback+ Robert! Asking for review from Dolske.
Attachment #511448 - Flags: review?(dolske)
Comment on attachment 511448 [details] [diff] [review]
[checked-in] proposed fix

rs=me
Attachment #511448 - Flags: review?(dolske)
Attachment #511448 - Flags: review+
Attachment #511448 - Flags: approval2.0+
Thanks for the review+ and approval, Dolske!
Whiteboard: [patchclean:0210] → [patchclean:0210][checkin]
Comment on attachment 511448 [details] [diff] [review]
[checked-in] proposed fix

http://hg.mozilla.org/mozilla-central/rev/f02cf259f317
Attachment #511448 - Attachment description: proposed fix → [checked-in] proposed fix
Status: ASSIGNED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Whiteboard: [patchclean:0210][checkin] → [patchclean:0210]
we neglected to remove the extra destroy call in inspector.js which relies on the PropertyPanel.jsm.

fix is:

diff --git a/browser/base/content/inspector.js b/browser/base/content/inspector.js
--- a/browser/base/content/inspector.js
+++ b/browser/base/content/inspector.js
@@ -795,17 +795,16 @@ var InspectorUI = {
 
     if (this.isStylePanelOpen) {
       this.stylePanel.hidePopup();
     }
     if (this.domPanel) {
       this.domPanel.hidePopup();
       this.domBox = null;
       this.domTreeView = null;
-      this.propertyPanel.destroy();
     }
     this.inspectCmd.setAttribute("checked", false);
     this.browser = this.win = null; // null out references to browser and window
     this.winID = null;
     this.selection = null;
     this.treeLoaded = false;
     this.closing = false;
     Services.obs.notifyObservers(null, "inspector-closed", null);
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
checked in:

http://hg.mozilla.org/mozilla-central/rev/b6d820414fca
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Verified 

Mozilla/5.0 (Windows NT 6.1; rv:2.0b12) Gecko/20100101 Firefox/4.0b12
Status: RESOLVED → VERIFIED
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: