Security pane in Webconsole

[Tanvi Vyas]

Hi,

I see some recent changes to the Webconsole in Nightly. What happened
to the security pane? Was it intentionally left out of the new
webconsole UI?

Thanks!

~Tanvi

[Brian Grinstead]

By security pane do you mean the security filter dropdown? If so, security messages are visible by default in the new console. Filtering happens only on the severity level of messages instead (errors/warnings). There are some mockups at https://projects.invisionapp.com/share/GN527IGMZ#/screens/121551039 that explain that design (all the way at the bottom).

Brian

> _______________________________________________
> dev-developer-tools mailing list
> dev-devel...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-developer-tools

[Tanvi Vyas]

Hi Brian,

Yes, I mean the security filter drop down. I'm worried that the
security messages will get lost in the rest of the messages. I was
debugging something earlier this week, and had to go to the browser
console in order to find the security messages, since the web console
had so much going on.

~Tanvi

[Daniel Veditz]

I'll second that. I incorrectly told Tanvi those messages were removed from
the web console and ONLY available on the browser console because I
couldn't find them even when I was looking for them and knew they were
there.

-Dan Veditz

[Brian Grinstead]

So the workflow with the browser console filtering UI is to disable all non-security messages so you only see that type?

One thing that could help with the new filtering UI is disabling the ‘Logs’ button. You’d still see page errors caused by JS but it would also keep security warnings / errors visible and should remove most of the other messages. Does that help? There might be other things we could do to make this easier so I can follow up with UX that isn’t working for you.

Brian

> On Nov 17, 2016, at 11:35 PM, Daniel Veditz <dve...@mozilla.com> wrote:
>
> I'll second that. I incorrectly told Tanvi those messages were removed from the web console and ONLY available on the browser console because I couldn't find them even when I was looking for them and knew they were there.
>
> -Dan Veditz
>
> On Thu, Nov 17, 2016 at 5:19 PM, Tanvi Vyas <ta...@mozilla.com> wrote:
> Hi Brian,
>
> Yes, I mean the security filter drop down. I'm worried that the security messages will get lost in the rest of the messages. I was debugging something earlier this week, and had to go to the browser console in order to find the security messages, since the web console had so much going on.
>
> ~Tanvi
>
>
>
>
> On 11/15/16 3:30 PM, Brian Grinstead wrote:

> By security pane do you mean the security filter dropdown? If so, security messages are visible by default in the new console. Filtering happens only on the severity level of messages instead (errors/warnings). There are some mockups at https://projects.invisionapp.com/share/GN527IGMZ#/screens/121551039 that explain that design (all the way at the bottom).

[Daniel Veditz]

On Fri, Nov 18, 2016 at 9:40 AM, Brian Grinstead <bgrin...@mozilla.com>
wrote:

> So the workflow with the browser console filtering UI is to disable all
> non-security messages so you only see that type?
>

​You could do that, but on the Browser Console they look visually distinct
enough that I don't usually do that.

​


> One thing that could help with the new filtering UI is disabling the
> ‘Logs’ button. You’d still see page errors caused by JS but it would also
> keep security warnings / errors visible and should remove most of the other
> messages. Does that help? There might be other things we could do to make
> this easier so I can follow up with UX that isn’t working for you.
>

​It's usually the JS errors that hide it. Log messages seem to be in a
different color, and modern JS-heavy pages have reams of JS warnings. The
security messages I'm interested seem to also be classed as warnings so I
can't get rid of the noise without killing the signal.

​
-
​Dan Veditz​

[Brian Grinstead]

> On Nov 19, 2016, at 12:00 AM, Daniel Veditz <dve...@mozilla.com> wrote:
>
> On Fri, Nov 18, 2016 at 9:40 AM, Brian Grinstead <bgrin...@mozilla.com> wrote:
> So the workflow with the browser console filtering UI is to disable all non-security messages so you only see that type?
>
> ​You could do that, but on the Browser Console they look visually distinct enough that I don't usually do that.

Ah - security messages look just like any other error in the new frontend. I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1319136 to fix that.

Brian