从Firefox 51.0.1开始,console.log()在Firebug中不起作用 [英] console.log() doesn't work anymore in Firebug since Firefox 51.0.1

查看:99
本文介绍了从Firefox 51.0.1开始,console.log()在Firebug中不起作用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我刚更新了firefox到Firefox 51.0.1(32位),更新后console.log停止工作。

I've just updated firefox to a Firefox 51.0.1 (32-bit), and after the update console.log stopped working.

使用 console.log()来测试一些JavaScript变量,它不会输出任何东西。

When I am tring to test some JavaScript variables using console.log(), it doesn't output anything.

推荐答案

当我在在另一个答案中提到时,发生这种情况是因为Firebug使用的Firefox内部API输出数据,改变了。
当您打开浏览器控制台时,您会看到以下错误:
$ b

As I mentioned in another answer, this happens because the Firefox internal APIs, which Firebug uses to output the data, have changed. When you open the Browser Console, you'll see the following error:


TypeError:ConsoleAPIListener不是构造函数console.js:149:38

TypeError: ConsoleAPIListener is not a constructor console.js:149:38

请注意,正如 Firebug讨论组中的一个主题以及 Firebug主页上,Firebug已停止使用,无人维护。
I.e.随着每个新版本的Firefox都会越来越多,并且一旦启用了多进程的Firefox,就会完全退出。有博客文章解释原因

Note that, as stated in a thread in the Firebug discussion group and on the Firebug homepage, Firebug is discontinued and unmaintained. I.e. it breaks more and more with every new version of Firefox and will quit working completely once multi-process Firefox is enabled. There is a blog post explaining the reasons.

Firebug的团队建议使用 Firefox DevTools ,而且有一个移植指南可用。

The team behind Firebug advises to use the Firefox DevTools instead and there is a migration guide available.

这篇关于从Firefox 51.0.1开始,console.log()在Firebug中不起作用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆