Thread:Talk:Account creation user experience/Testing/Minor things/reply

1. That's a setting that is not due to the redesign. 2. That's just due to the nature of how we're testing it. You just need to re-add &useNew=1 on the HTTPS login form to see it. When it's enabled by default it won't have this problem. 3. Good point. We didn't think about this, since while the old login form often had a custom message on it to suggest HTTPS, the account creation form never has. We'll try to think about how to incorporate it.