It will be in a web developer pack in our installer.
*** Bug 213949 has been marked as a duplicate of this bug. ***
Users still need a way to see that an error is with the web site, not the browser configuration. Otherwise, we will end up with a lot of invalid bugs or new sites that webmasters tested in Firebird and got no errors.
Also think it is important for End Users to see, if there happens some errors in the page. However we still fighting against some sites "optimized" for the Internet Explorer that occures some errors in java script in Firebird. A feedback about the error that prefend the correct using of the website would stop irrtitating the user. The current way is still better solved than the way the IE do. But maybe it would be a nice additional work to show a small icon at the bottom left to show that the site caused an error, similar to the IE. As a web developer I also would like such a feature.
Statusbar notification extension. But it needs a little work. http://extensionroom.mozdev.org/#jsstatus
I agree with comment 3. There should be a cleaner, more user friendly method for end users. Web Developers should get the more detailed flexible js console... to the end user it's confusing.
14 years ago
Does this problem argue about the installer package of windows? Is it the meaning that Java Script Console is not chosen in standard installation? Or is it the meaning to deleting from a package completely? Now, there is no installer package of a Mac-OS-X version. (That is, there is no means to choose this function at the time of installation.) When deleted completely, people to use these functions are troubled.
This tool is great! Do You prefer MSIE JS behaviour?
13 years ago
-> js console.
Unlikely, at this point. Certainly not blocking bug 171082, since it was about the custom install option, not about an extension or a stub installer that would take it clear out of the download.
Marking resolved fixed as we now have a built-in web console and scratchpad which amply cover the needs of this bug.
Isn't the browser console Firefox-only? This bug is for Toolkit.
> Isn't the browser console Firefox-only? This bug is for Toolkit. Oh good point. I'll reopen, or perhaps repurpose this bug to move the web console and scratchpad to toolkit.
The Error Console has been removed in favor of the Browser Console (see Bug 1278368), and the component is going to be removed. If this bug is also relevant in the Browser Console, please reopen and move this into Firefox -> Developer Tools: Console.
I am mass-reopening and re-componenting every single one of the Toolkit:Error Console bugs that appear to have been closed without anyone even *glancing* at whether they were relevant to the Browser Console. If you want to close a whole bunch of old bugs -- FOR ANY REASON -- it is YOUR RESPONSIBILITY to check EVERY SINGLE ONE OF THEM and make sure they are no longer valid. Do not push that work onto the bug reporters. (It's okay to close bugs that haven't been touched in years when they don't have enough information for you to figure out whether the problem is still relevant to the current software - the reporter probably isn't coming back to clarify. But that is the ONLY situation where it is okay.) (I'm going to have to do this in two steps because of the way the "change several bugs at once" form works. Apologies for the extra bugspam.)
The Browser Console has been ported to toolkit