How to hide permanently these errors? (Password fields present on an insecure (http://) page. This is a security risk that allows user login credentials to be stolen.)

9,782 views
Skip to first unread message

Ned

unread,
Feb 25, 2014, 9:48:53 PM2/25/14
to fir...@googlegroups.com
I have this warning in firebug console and I can't get rid of them permanently.  Are those Firebug errors or Firefox console errors? 

I've already tried with userChrome.css

menuitem[label="Error Console"] {display: none !important;}

but is not working.

Any idea on how to hide PERMANENTLY these errors? 

Thanks

Ned


screenshot.12.jpg

Jan Honza Odvarko

unread,
Feb 26, 2014, 2:12:36 AM2/26/14
to fir...@googlegroups.com
These errors comes from the page and are displayed by Firebug
(they should be visible even in Firefox web console I guess)


> menuitem[label="Error Console"] {display: none !important;}
> but is not working.
yeah, this this rule is not related to Firebug UI

I don't see any meaningful way how to avoid them except fixing the page ;-)

Honza

Sebastian Zartner

unread,
Feb 26, 2014, 7:50:56 AM2/26/14
to fir...@googlegroups.com
> menuitem[label="Error Console"] {display: none !important;}
> but is not working.
yeah, this this rule is not related to Firebug UI

I don't see any meaningful way how to avoid them except fixing the page ;-)

On a local webserver the people sometimes don't have an SSL certificate installed, so I can understand the request. One way to get rid of such messages is described in issue 4368.
Though generally security hints should not be ignored.

@Honza: The 0 as source text is a bit strange. I guess we should fix that.

Sebastian

Sebastian Zartner

unread,
Feb 26, 2014, 7:52:35 AM2/26/14
to fir...@googlegroups.com
Btw. there's a detailed description of all security warnings:

https://developer.mozilla.org/de/docs/Tools/Web_Console#Security_warnings_and_errors

Sebastian

Jan Honza Odvarko

unread,
Feb 26, 2014, 7:54:40 AM2/26/14
to fir...@googlegroups.com
> @Honza: The 0 as source text is a bit strange. I guess we should fix that.
Sure, find a testcase, STR and report and issue for it.
Honza


On Wednesday, February 26, 2014 1:50:56 PM UTC+1, Sebastian Zartner wrote:

Sebastian Zartner

unread,
Feb 26, 2014, 8:25:38 AM2/26/14
to fir...@googlegroups.com
> @Honza: The 0 as source text is a bit strange. I guess we should fix that.
Sure, find a testcase, STR and report and issue for it.
Created issue 7209.

Sebastian

Sebastian Zartner

unread,
Feb 26, 2014, 5:51:35 PM2/26/14
to fir...@googlegroups.com
Firebug currently (1.12.6) incorrectly categorizes those message as JavaScript errors. So I created another issue to change that. Just to note, these messages come from Firefox, Firebug just displays them.
What you can do now:
  1. Set up an HTTPS connection for your website. (recommended in case the page is online)
  2. Help us implement issue 7214 or issue 4368.
  3. Uncheck the Console panel option Show JavaScript Errors. (Though then you also won't see real JavaScript errors anymore.)
  4. Keep using the search field for filtering the messages.
  5. Just ignore those messages.

Sebastian

 
I've read that page and I didn't find any way to get rid of the message (except using search, but I want a permanent solution, I don't want to type every time I reload the page). I've read other issues and link from that page but I didn't find anything usefull

I don't think it's a big deal to add a filter by regexp or something like similar to filter kind of error permanently. It's up to me if I want to see that or not. I always use firebug open a bit and those messages are always filling my whole window!

Arthur Shpakov

unread,
Mar 11, 2014, 2:55:04 PM3/11/14
to fir...@googlegroups.com
Please fix this issue by letting people disable these error messages.
There are tons of websites using passwords without ssl.
This messages is really annoying.
I understand the risks and can live with them.
I mean this warning is helpful only once, but one should decide on his own if he will fix this issue or not.

Sebastian Zartner

unread,
Mar 11, 2014, 3:26:32 PM3/11/14
to fir...@googlegroups.com
We're currently focus on issue 5421 and don't have the resources to work on this right now.
So as I said in my previous comment you may want to help us by providing a patch for issue 7214 or issue 4368.

Sebastian
Reply all
Reply to author
Forward
0 new messages