Firebug console: not showing console.log

beckah picture beckah · Mar 19, 2014 · Viewed 34.4k times · Source

I am trying to test something, and for one reason or another, while working in the Firebug console, I am unable to create an array of script tags on the HTML page using the getElementByTagName('script') method. I realize there is probably something stupid I am overlooking.

This is the dummy HTML page:

<html>
<head>
    <title>Random Crapolla Page</title>
    <h1>Random Crapolla Page</h1>
</head>

<body>
    <div id="whyNot">
    <p id="p1">
        <a href="http://google.com">Here is link one</a><br />
        <a href="http://google.com">Oh poop here's another</a><br />
        <a href="http://google.com">And a 3rd for good measure</a><br />
    </p>

    <a id="p2">
        Latin. Latin. Latin...<br />
        Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum
    </p>
    </div>
    <!-- Script tag testing-->
    <script type="text/javascript" src="itDoesntExist.js"></script>
    <script type="text/javascript" src="dummyJSnumeroDos.js"></script>
</body>

And this is what I'm typing into the Firebug console:

var scripts = document.getElementsByTagName('script');
console.log(scripts);

enter image description here


All selected in Console enter image description here

Answer

Sebastian Zartner picture Sebastian Zartner · Feb 28, 2017

Firebug is officially discontinued now and the console output is broken in Firefox 51.0.1 due to a change in the Firefox internal APIs Firebug uses to access the related data. For reference, this is the error:

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

Firebug users are advised to switch over to the Firefox DevTools instead. There, the console output works as expected.