5 ms·

Very cool. I just signed up, but was a bit frustrated by the hijacked experience for sign-up as it broke my LastPass plugin to generate and save my password. J

Very cool. I just signed up, but was a bit frustrated by the hijacked experience for sign-up as it broke my LastPass plugin to generate and save my password. Just wanted to point this out.

keithwhor 7y ago
That’s great feedback, thank you! We’ll definitely see if we can test across a few different password managers / signup experiences to make sure it’s a smoother process.
- bestest 7y ago
  Same here. Was expecting Safari to suggest a password, yet it did not. By inspecting the cause I was appalled to see custom inputs! Mother of dragons!
  - chairmanwow1 7y ago
    Honest question: what would compel someone into making a decision like this?
    - keithwhor 7y ago
      You mean why would somebody build custom inputs? We need our inputs on Autocode to do a whole ton of custom stuff; support emoji insertion, allow for an autocomplete dropdown, support typeahead autocomplete, have multiple layers for syntax highlighting (code editor). So we roll our own components for a lot of this stuff. We don't have problems with every password manager; the raw HTML input element is still there. I think it's probably an easy fix, we just gotta look into it.
      - wise_young_man 7y ago
        None of those use cases apply for authentication though right? Or are people using emojis for logins now? Even if they were, standard browser form input I’m sure would handle them fine natively.
        keithwhor 7y ago
        (1) Design systems and components. We'd rather use the same thing everywhere, if possible. (Unless of course, it disrupts user login and end-user experience... which is why we'll look into making it better!) (2) I actually think this can be fixed with a few HTML attribute changes but I won't know for sure until I dig in. If you can imagine, we have a laundry list of items piling up to take care of :)
        presumably 7y ago
        For (2), you may find the section 'Other useful autocomplete values' from this article helpful: https://www.twilio.com/blog/html-attributes-two-factor-authentication-autocomplete https://www.twilio.com/blog/html-attributes-two-factor-authe... Discussed on HN: https://news.ycombinator.com/item?id=22022106 https://news.ycombinator.com/item?id=22022106
      - chairmanwow1 7y ago
        This makes sense to me. Thanks for the response~ Learned a lot

Very cool. I just signed up, but was a bit frustrated by the hijacked experience for sign-up as it broke my LastPass plugin to generate and save my password. Just wanted to point this out.

keithwhor 7y ago

That’s great feedback, thank you! We’ll definitely see if we can test across a few different password managers / signup experiences to make sure it’s a smoother process.

bestest 7y ago
Same here. Was expecting Safari to suggest a password, yet it did not. By inspecting the cause I was appalled to see custom inputs! Mother of dragons!
- chairmanwow1 7y ago
  Honest question: what would compel someone into making a decision like this?
  - keithwhor 7y ago
    You mean why would somebody build custom inputs? We need our inputs on Autocode to do a whole ton of custom stuff; support emoji insertion, allow for an autocomplete dropdown, support typeahead autocomplete, have multiple layers for syntax highlighting (code editor). So we roll our own components for a lot of this stuff. We don't have problems with every password manager; the raw HTML input element is still there. I think it's probably an easy fix, we just gotta look into it.
    - wise_young_man 7y ago
      None of those use cases apply for authentication though right? Or are people using emojis for logins now? Even if they were, standard browser form input I’m sure would handle them fine natively.
      - keithwhor 7y ago
        (1) Design systems and components. We'd rather use the same thing everywhere, if possible. (Unless of course, it disrupts user login and end-user experience... which is why we'll look into making it better!) (2) I actually think this can be fixed with a few HTML attribute changes but I won't know for sure until I dig in. If you can imagine, we have a laundry list of items piling up to take care of :)
        presumably 7y ago
        For (2), you may find the section 'Other useful autocomplete values' from this article helpful: https://www.twilio.com/blog/html-attributes-two-factor-authentication-autocomplete https://www.twilio.com/blog/html-attributes-two-factor-authe... Discussed on HN: https://news.ycombinator.com/item?id=22022106 https://news.ycombinator.com/item?id=22022106
    - chairmanwow1 7y ago
      This makes sense to me. Thanks for the response~ Learned a lot