search

mozilla / r2d2b2g

Firefox OS Simulator is a test environment for Firefox OS. Use it to test your apps in a Firefox OS-like environment that looks and feels like a mobile phone.
https://addons.mozilla.org/en-US/firefox/addon/firefox-os-simulator/
Other
392 stars 139 forks source link

"The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page" #821

Open sole opened 11 years ago

sole commented 11 years ago

I don't know what has happened or what I'm possibly doing wrong, but after trying with Nightly, Aurora, Beta and Stable I can't get the simulator to stop emitting that message , and I can't get the console.* methods to work, either.

The only references to that message I could find in the internet are in fact mentions to Firebug, which I do not have installed, so I'm much puzzled about this.

Is there anything I can do?

sole commented 11 years ago

Correction: the console.* methods work. But the message is still there o_O

This gets downgraded to a puzzling cosmetic issue, then :)

hanklank commented 11 years ago

I get the same message, but for me console doesn't work. I removed all other plugins and restarted, stil get the message when running simulator app.

Environment: Ubuntu 13.04 x64 Latest firefox 0S simulator 5, pre3 No other addons installed Firefox 23.

jrconlin commented 10 years ago

I believe this message is triggered when the console is replaced by an object: https://github.com/mozilla/mozilla-central/blob/23749a301a607174e6363010edc9f42348dd2740/browser/devtools/webconsole/webconsole.js#L1543

It may be that this is triggered by a emulated file "replacing" the console with itself. I also see the message, but console messages from inside my webapp are sent to the connected debugger terminal (Firefox 27.0a1 | Windows 7). It might be useful to add a bit of clarification to the docs about this and clear up if it's an error or a byproduct warning.

dbdavis commented 7 years ago

This problem was driving mr nuts. How can I debug with no console, alerts only take you so far. I looked at all of the many other comments. Although 1 of them mentioned that it was due to firebug; none of them mentioned that, although the firefox (and I would guess other) browser console was useless, the desired console output shows up in the firefox console. Look there! Now I can proceed.