In my opinion, self-signed SSL certificates shouldn't cause this. If I want to use an SSL connection for my users to sign in with, I shouldn't have to pay tons of money for a wildcard certificate for my domain (they charge a large amount more just to add *. to your certificate). SSL is to SECURE THE TRANSMISSION, but these companies have turned it into a certificate war, where you must have one signed by a "distinguished" CA or the browser will tell you that you're visiting a "bad" site (Mozilla has a stopping guard, IE has attention images).
So don't even show the user that it's SSL. I don't care if my site seems more secure to the end-user, it just should be SECURE without regard to the mindset of the individual operating on it. Heck, even hide the https! Banks and online stores, sure, they should buy SSL certificates so they ease the end-user's mind. That is a relevant operating cost to incur for those individuals.
So don't even show the user that it's SSL. I don't care if my site seems more secure to the end-user, it just should be SECURE without regard to the mindset of the individual operating on it. Heck, even hide the https! Banks and online stores, sure, they should buy SSL certificates so they ease the end-user's mind. That is a relevant operating cost to incur for those individuals.