I think this bug is rather important, and we've made no progress in addressing it. Here are some ways we could try:
Have those yellow popups, like the ones that NoScript uses out of the box. They're very annoying, and the first thing you want to do is turn them off, but people do notice them.
Animate the HTTPS Everywhere logo when it's active. That will make it stand out more.
Open a new tab after first install, which points out the menu and shows how to use it.
I've started work on a potential solution and am still messing around with which method might be best. Of course it might take a while until I can showcase something.
One potential solution that I'm leaning towards is after startup, having the browser open a new tab and print a notification at the top. The new tab would point to "https://www.eff.org/https-everywhere/faq." For how this would look, I've added an attachment. Any thoughts?
Micah, nullthree/nullishzero's nice starting patch for this has landed in master, but I think we should do a UI review to see what if any extra polish we can add.
I was just looking at this UI feature again in preparation for a 4.0dev7 release. I think the existing patch is good enough for that release, an improvement we could make is to align the text over on the right side of the notification box, and end it with an arrow of some sort that points upward. It'll require some multi-platform testing to be certain, but I think in most or all cases that arrow will wind up pointing at the HTTPS Everywhere button that's just been added to the toolbar.
I'm not sure if that's possible with simple XUL CSSery, or whether we'll need to use this sort of method. I just tried this, but it didn't seem to work.
I was just looking at this UI feature again in preparation for a 4.0dev7 release. I think the existing patch is good enough for that release, an improvement we could make is to align the text over on the right side of the notification box, and end it with an arrow of some sort that points upward. It'll require some multi-platform testing to be certain, but I think in most or all cases that arrow will wind up pointing at the HTTPS Everywhere button that's just been added to the toolbar.
I'm not sure if that's possible with simple XUL CSSery, or whether we'll need to use this sort of method. I just tried this, but it didn't seem to work.
Hi pde,
I'll take a look into seeing if I can make the improvement suggested. I'm hoping it's possible with simple XUL CSSery, but I wouldn't mind writing a custom notification if needed.
Give me a few days, and I'll see if I can put something together by Monday (05/11/13). I'll test it on Windows XP/7 and GNU/Linux (I'm on Gentoo).
Hmm... looks like aligning the text right isn't as trivial as I thought. There is a CSS trick you could do to align the text right, but it doesn't work well; the alignment is closer to the center than to the right. Also, based on my testing, having an arrow may not point correctly if there are other plugins (e.g. ghostery + firebug).
Another potential solution might be to have a button on the notification...
Also, based on my testing, having an arrow may not point correctly if there are other plugins (e.g. ghostery + firebug).
This is annoying :(
I wonder if there's a way to use CSS introspection to figure out how far from the right hand side we are, and set a corresponding offset. Micah, do you have any ideas about that?
Another potential solution might be to have a button on the notification...
Yes but since we don't want to have the notification open all the time, that doesn't seem like a good idea. NoScript does something like this by default, and I find it Extremely Annoying because it takes up so much screen space.
Micah, should we close this bug, or should we try harder to some kind of XUL/CSS introspection to figure out where the toolbar button is, and point at it?
Micah, should we close this bug, or should we try harder to some kind of XUL/CSS introspection to figure out where the toolbar button is, and point at it?
pde, have you merged nullishzero's commits? If you have, I think just showing the number of rules is good and we can close this bug.