Disabling Content in the Error Console
Rob Campbell
Just a heads-up: This week, I'm going to land bugs 602006, remove Error Console Menu Items (pending a new patch) and bug 593540[2], Disable Content Errors in the Error Console.
This will make the Error Console primarily useful for debugging Chrome errors and not content. To see errors from content, you'll have to use the Web Console. Note that the shortcut key, (Ctrl/Cmd-Shift-J) will still be operational for the Error Console and won't require an explicit pref setting to enable it.
Cheers,
Rob Campbell
[1] - https://bugzilla.mozilla.org/show_bug.cgi?id=602006
[2] - https://bugzilla.mozilla.org/show_bug.cgi?id=593540
Boris Zbarsky
> Just a heads-up: This week, I'm going to land bugs 602006, remove Error Console Menu Items (pending a new patch) and bug 593540[2], Disable Content Errors in the Error Console.
>
> This will make the Error Console primarily useful for debugging Chrome errors and not content. To see errors from content, you'll have to use the Web Console.
Unless I'm missing something, errors that happened prior to opening the
Web Console are still not shown in it. This, combined with the
inability to put it in a separate window, makes it a serious PITA for
most of the things I use the Error Console for...
Pending those issues being addressed, can we at least leave an option to
show content errors in the Error Console?
-Boris
"mitcho (Michael 芳貴 Erlewine)"
+1. This could be a major issue for Panorama dev as well, at least while the web console can't be pulled up for the Panorama iframe (bug 592003).
mitcho
--
mitcho (Michael 芳貴 Erlewine)
mit...@mitcho.com
http://mitcho.com/
linguist, coder, teacher
Rob Campbell
Ah, thanks for reminding me. Part of the patch in bug 593549 creates a pref "devtools.errorconsole.showContent". Setting that to true will return content errors to the Error Console.
There are a number of patches to start caching errors for the Web Console before opening it. Not sure if they'll make it in this week or not. My fingers are crossed!
~ rob
Rob Campbell
> On Feb 8, 2011, at 12:18 PM, Boris Zbarsky wrote:
> +1. This could be a major issue for Panorama dev as well, at least while the web console can't be pulled up for the Panorama iframe (bug 592003).
Note that you'll still get errors from Chrome without tweaking any prefs. This patch will actually make the Error Console that much better for debugging chrome as you won't end up filling it with a bunch of unrelated content errors. A problem I've run into on a number of occasions while hacking on the browser.
cheers,
Rob
Mike Shaver
> Hi,
>
> Just a heads-up: This week, I'm going to land bugs 602006, remove Error Console Menu Items (pending a new patch) and bug 593540[2], Disable Content Errors in the Error Console.
I don't think we should do this until the patches to fix the various
issues with the Web Console (copy/paste, line-number linking, caching,
etc.) are resolved, and we're sure we like how it ended up. I don't
know of anyone who is running with all the patches combined, but maybe
they're in a repo somewhere.
Otherwise we are committed to a path that we don't need to commit to
in order for FF4 to be successful. The Web Console is nice to have,
but removing the Error Console entry seems like something that is not
critical to our release and we should therefore take neither the UI
disruption nor the associated risk, especially without having lived in
the fully-formed Web Console for a little while. Switching the
defaults in FF5 once we have reacted to developer feedback in the wild
seems better to me, especially given this very very late date.
Mike
Kevin Dangoor
> Otherwise we are committed to a path that we don't need to commit to
> in order for FF4 to be successful. The Web Console is nice to have,
> but removing the Error Console entry seems like something that is not
> critical to our release and we should therefore take neither the UI
> disruption nor the associated risk, especially without having lived in
> the fully-formed Web Console for a little while. Switching the
> defaults in FF5 once we have reacted to developer feedback in the wild
> seems better to me, especially given this very very late date.
>
>
Assuming that users won't be confused by "Error Console" and "Web Console"
as separate menu items that appear together, I agree with you. The question
of when to use one or the other might be confusing, though it's easy for
developers to decide for themselves just by opening the consoles and seeing
what they are presenting and how they present it.
And, for what it's worth, I've seen nothing from Input where people were
confused, so maybe I need not worry about such things.
Kevin
--
Kevin Dangoor
work: http://mozilla.com/
email: kdan...@mozilla.com <k...@blazingthings.com>
blog: http://www.BlueSkyOnMars.com
Mike Shaver
> Assuming that users won't be confused by "Error Console" and "Web Console"
> as separate menu items that appear together, I agree with you. The question
> of when to use one or the other might be confusing, though it's easy for
> developers to decide for themselves just by opening the consoles and seeing
> what they are presenting and how they present it.
I don't think we should flip the error console show-in-content pref
either. I think we should make the Web Console good enough that
people will prefer to use it, and evangelize it, but not take out
long-standing functionality at this extremely, very,
I-think-you-get-the-point late date.
Mike
Kevin Dangoor
> I don't think we should flip the error console show-in-content pref
> either. I think we should make the Web Console good enough that
> people will prefer to use it, and evangelize it, but not take out
> long-standing functionality at this extremely, very,
> I-think-you-get-the-point late date.
>
>
I agree that the same logic applies to that patch as well. I'll make notes
in the relevant bugs.
EE
What is the web console? I have never seen it.
Rob Campbell
On 2011-02-08, at 15:05 , Kevin Dangoor wrote:
> On Tue, Feb 8, 2011 at 1:37 PM, Mike Shaver <mike....@gmail.com> wrote:
> I don't think we should flip the error console show-in-content pref
> either. I think we should make the Web Console good enough that
> people will prefer to use it, and evangelize it, but not take out
> long-standing functionality at this extremely, very,
> I-think-you-get-the-point late date.
>
>
> I agree that the same logic applies to that patch as well. I'll make notes in the relevant bugs.
Very well then!
~ rob
Rob Campbell
Ctrl/Cmd-Shift-K in Firefox 4.
~ rob
Natch
> On 2011-02-08, at 15:11 , EE wrote:
>
> > On 2011/02/08 9:33, Rob Campbell wrote:
> >> Hi,
>
> >> Just a heads-up: This week, I'm going to land bugs 602006, remove Error Console Menu Items (pending a new patch) and bug 593540[2], Disable Content Errors in the Error Console.
>
> >> This will make the Error Console primarily useful for debugging Chrome errors and not content. To see errors from content, you'll have to use the Web Console. Note that the shortcut key, (Ctrl/Cmd-Shift-J) will still be operational for the Error Console and won't require an explicit pref setting to enable it.
>
> >> Cheers,
> >> Rob Campbell
>
> >> [1] -https://bugzilla.mozilla.org/show_bug.cgi?id=602006
>
> > What is the web console? I have never seen it.
>
> Ctrl/Cmd-Shift-K in Firefox 4.
>
> ~ rob
Would be nice to get the patch in with the default set to show the
content errors (and menu items). This way it's a simple change in the
future and current users that would like to change the error console
can do so...