Closed Bug 1083508 Opened 10 years ago Closed 10 years ago

console functions don't work

Categories

(Firefox :: Untriaged, defect)

33 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: Enyby, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141011015303

Steps to reproduce:

Run in firebug or in page any of functions console:
console.log('test');
or
console.dir('test');


Actual results:

TypeError: console.log is not a function


Expected results:

'test'
If type only "console" output show next functions:
Object { log=function(), debug=function(), info=function(), ещё...}
Content assist show all functions.

But any of this is not accessible.

If you type: "console.log" it's show "undefined".
"typeof console.log" -> "undefined"
"typeof console" -> "object"

It's happens after update FF to 33 version.
WFM with FF33 win 7.

Could you test:
1) in safe mode: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
2) with a clean profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Does it fix it?
Flags: needinfo?(Enyby)
In safe mode work fine.
In normal mode work, but after start firebug I have strange error:

XrayWrapper denied access to property log (reason: value is callable). See https://developer.mozilla.org/en-US/docs/Xray_vision for more information. Note that only the first denied property access from a given global object will be reported.

After that functions broken.
Flags: needinfo?(Enyby)
Add-on issue, probably. Try to disable htem one by one to find the culprit.
> typeof console.wrappedJSObject.log;
"function"
> console.wrappedJSObject.log('test');
Object {  }
> typeof console.log;
"undefined"

"console.wrappedJSObject.log" is function and callable, but produce unexpected results. It's in normal mode.
Probaly it's problem with Xray. Firebug don't know about this. May be it create own wrappers on console functions.
Update Firebug from 2.0.1 to 2.0.4 fix issue.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.