1Password writing over data in fields?

PatriciaW

<div class="IPBDescription">Feature request?</div>I was completing a multi-stage form to order bus tickets. First I had to enter the passenger names which I did ... myself and another person ... then I had to enter the billing information and address. I used 1Password wallet and identities to do this. When I got my eTickets I discovered to my horror that both tickets were in the same name (mine). Ultimately I realized that 1Password must have changed the name that was already on the form to my name. Since the ticket is non-refundable and non-transferable this will probably cost me money unless I can convince the bus company to correct the mistake.



Would it be possible to modify 1Password to provide an alert if it is going to overwrite data in a field?

[Deleted User]

Hi Patricia,



I'm really sorry for the trouble here, and I'm sorry to hear that this may cost you money, hopefully the bus company will understand and help you out.



The problem is that 1Password doesn't read the content of the web form itself, it looks at the field names associated with the form, and to try and actually improve form filling in general it will fill your name anywhere where there's a valid name field when you use an Identity. In general this is a good thing, but obviously we'd advise you to always check the form before you submit, especially if there are multiple fields for names for different purposes on a single page.



Do you have a link to the bus company's site and I can take a look at the code and see if there's anything we can possibly do for cases like this.



Thanks,





[quote name='PatriciaW' timestamp='1301492576' post='23547']

I was completing a multi-stage form to order bus tickets. First I had to enter the passenger names which I did ... myself and another person ... then I had to enter the billing information and address. I used 1Password wallet and identities to do this. When I got my eTickets I discovered to my horror that both tickets were in the same name (mine). Ultimately I realized that 1Password must have changed the name that was already on the form to my name. Since the ticket is non-refundable and non-transferable this will probably cost me money unless I can convince the bus company to correct the mistake.



Would it be possible to modify 1Password to provide an alert if it is going to overwrite data in a field?

[/quote]

PatriciaW

[quote name='stu' timestamp='1301502312' post='23571']

Hi Patricia,



I'm really sorry for the trouble here, and I'm sorry to hear that this may cost you money, hopefully the bus company will understand and help you out.



The problem is that 1Password doesn't read the content of the web form itself, it looks at the field names associated with the form, and to try and actually improve form filling in general it will fill your name anywhere where there's a valid name field when you use an Identity. In general this is a good thing, but obviously we'd advise you to always check the form before you submit, especially if there are multiple fields for names for different purposes on a single page.



Do you have a link to the bus company's site and I can take a look at the code and see if there's anything we can possibly do for cases like this.



Thanks,

[/quote]



The bus company is Greyhound and their site is Greyhound.ca



Greyhound wasn't at all sympathetic to my plight and refused to do anything other than let me apply for a credit for the non-refundable ticket when I purchase another full-fare ticket ... which isn't much of a break because the full-fare is about twice the discounted fare.



Normally I notice things like this but because the form had scrolled down to the billing info (and I think hidden the other areas of the form) I did not realize what had happened until I printed the tickets.

khad

Thanks for the link, Patricia. I will pass this along to the developers to see if there is anything we can do to improve this.



Like Stu, I am truly sorry to hear that this happened.



[quote]Normally I notice things like this…[/quote]

I think that's the way these sorts of things always go. I find myself trusting 1Password so much that every once in a while I forget to double check that everything is filled in properly before submitting a form. I have been fortunate, but this is a reminder to me to always "look both ways" before submitting a form — especially one that has my credit card number in it. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_worried.png' class='bbc_emoticon' alt=':S' />



I looked up your record in our system and have sent you an email with an offer I hope will show that we understand your frustration. Regardless of whose "fault" it was, we think that you deserve a break. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



I hope it helps. I look forward to your response.

PatriciaW

[quote name='khad' timestamp='1301902793' post='23890']

Thanks for the link, Patricia. I will pass this along to the developers to see if there is anything we can do to improve this.



Like Stu, I am truly sorry to hear that this happened.





I think that's the way things sorts of things always go. I find myself trusting 1Password so much that every once in a while I forget to double check that everything is filled in properly before submitting a form. I have been fortunate, but this is a reminder to me to always "look both ways" before submitting a form — especially one that has my credit card number in it. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_worried.png' class='bbc_emoticon' alt=':S' />



I looked up your record in our system and have sent you an email with an offer I hope will show that we understand your frustration. Regardless of whose "fault" it was, we think that you deserve a break. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



I hope it helps. I look forward to your response.

[/quote]



Thanks for your offer and concern.



I definitely was guilty of trusting 1Password a bit too much in this case and don't blame it for my lack of attention. But if anything can be done to notify a user that they are about to do something like this I think it might prevent them from shooting themselves in the foot.

khad

Thanks for following up, Patricia.



I agree, and we have been internally discussing the issue you raised and really appreciate you bringing it to our attention!



If we can be of further assistance, please let us know.



We are always here to help!