Closed Bug 862916 Opened 12 years ago Closed 12 years ago

console.dir() gives blank box if logging filter was off while doing console.dir()

Categories

(DevTools :: Console, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 23

People

(Reporter: Optimizer, Assigned: msucan)

Details

Attachments

(1 file)

STR (in a latest nightly) : 1) Open Web Console 2) Have Logging filter off (all sorts of logging) 3) In the input area, type console.dir(window); 4) undefined comes as output. That is okay. 5) Turn on the logging filter. 6) You see blank box with heading [object Proxy] 7) Repeat step 3 and 4, everything normal now.
OS: Windows 7 → All
Priority: -- → P2
Hardware: x86_64 → All
Assignee: nobody → mihai.sucan
Status: NEW → ASSIGNED
Attached patch proposed fixSplinter Review
Problem was that the iframe doesn't load if the iframe itself (or any other parent) is display:none. openVariablesView() throws an exception in onContainerReady (window.document is undefined), but promises hide the exception (meh). This patch avoids the use of display:none for such messages until openVariablesView() is done. Added a test that confirms the fix works.
Attachment #744758 - Flags: review?(past)
Blocks: 869003
No longer blocks: 869003
Comment on attachment 744758 [details] [diff] [review] proposed fix Review of attachment 744758 [details] [diff] [review]: ----------------------------------------------------------------- Nice and clean. ::: browser/devtools/webconsole/test/browser_bug_862916_console_dir_and_filter_off.js @@ +24,5 @@ > + registerCleanupFunction(() => hud.setFilterState("log", true)); > + > + content.wrappedJSObject.fooBarz = "bug862916"; > + hud.jsterm.execute("console.dir(window)"); > + hud.jsterm.once("variablesview-fetched", (aEvent, aVar) => { Unrelated to this patch, but at some point we should look into harmonizing the event names across our tools, particularly for events that originate from the same components.
Attachment #744758 - Flags: review?(past) → review+
(In reply to Panos Astithas [:past] from comment #3) > Comment on attachment 744758 [details] [diff] [review] > proposed fix > > Review of attachment 744758 [details] [diff] [review]: > ----------------------------------------------------------------- > > Nice and clean. Thanks for the review! > ::: > browser/devtools/webconsole/test/ > browser_bug_862916_console_dir_and_filter_off.js > @@ +24,5 @@ > > + registerCleanupFunction(() => hud.setFilterState("log", true)); > > + > > + content.wrappedJSObject.fooBarz = "bug862916"; > > + hud.jsterm.execute("console.dir(window)"); > > + hud.jsterm.once("variablesview-fetched", (aEvent, aVar) => { > > Unrelated to this patch, but at some point we should look into harmonizing > the event names across our tools, particularly for events that originate > from the same components. Good point. Patch landed: https://hg.mozilla.org/integration/fx-team/rev/13c1c11245ab
Whiteboard: [fixed-in-fx-team]
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 23
The style rules for .hidden-message should not be in /skin/, but in /content/ as it is not styling, but functionality.
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: