Even smarter form recognition

Kobes

Hi Agilebits, I am fully aware that this request will be an edge case because you won't be finding a lot of sites on the web that employ this majorly annoying tactic. However, I have a bank site where no normal form fields are being used, but a password type field twice with a data-attribute hidden in the code to distinguish the two.

It would be awesome if 1P was able to figure out that it should save both items in separate fields in de 1P database, because now it keeps resetting the password.

I would understand if this wouldn't make it in a release, but I also couldn't help but ask :D

MikeT

Hi @Kobes,

Always bring up those edge cases with us. It is better to ask and know for sure we can't do it than to not ask and assume we can't do it when there's a chance we can. :) The edge cases can help us figure out a better alternative for this or even improve our current code to work with it.

I've filed a detailed report on this site and we will investigate for a magic solution on this. The dual-forms layout with the data-bind attributes is very awkward. I bet it'd also mess with the accessibility tools to help folks hear what the field is for.

Kobes

Hi Mike,
sorry for replying this late. Any way, thanks for responding and taking it very seriously. Happy to supply every edge case I run into :)

I don't think there are many sites having this particular implementation and apparently this bank is moving away from this craziness, too. I have reported this issue to them (along with the quite pathetic limitations on password complexity, it really bugs me to try 20 different generated passwords before I finally have one that a bank site allows). And in response to that they reported that they are busy reworking their login procedures. So, who knows that it'll be sorted out in a couple of months anyway.

Thanks again!

Megan

Hi @Kobes,

Thanks for the update! Here's to hoping that the bank's new login procedures will be much less crazy. :)