Substack's UI and 1Password temporarily cost me $2k

Re:Substack's UI and 1Password temporarily cost me $2k by irjustin on Monday March 22, 2021 @09:17PM (#26549782)

Probably not fair to pin it fully on 1pw or substack.

1PW autofills based on common cc form names, year, credit_card[year] etc etc. Substack clearly named the field a name that could hit that, probably amount_per_year.

1PW can't account for every form on every website, just not realistic.

How's the headline not true? It's a UI/UX issue that caused him to be charged that amount?

[ Parent | on HN ]

Re:Substack's UI and 1Password temporarily cost me $2k by IncRnd on Monday March 22, 2021 @09:19PM (#26549797)

1Pass can choose not to put CC information into hidden fields.

[ Parent | on HN ]

Re:Substack's UI and 1Password temporarily cost me $2k by nrmitchi on Monday March 22, 2021 @09:21PM (#26549808)

Looking at the screen cap, it's not actually a hidden form, as much as a form field styled to look like text.

[ Parent | on HN ]

Re:Substack's UI and 1Password temporarily cost me $2k by kalleboo on Monday March 22, 2021 @11:32PM (#26550768)

Looking at the source of the actual page, it's very odd markup.

There's a real input field, and a hidden input field "on top of" each other. I guess one is the stylized user-interactive one of which the value gets normalized into cents into the hidden one?

   <span class="variable-amount">
   $
   <input class="variable-amount-input" type="text" style="width: 25px;">
   <input name="amount" type="hidden" value="19900">
   /year
   </span>

[ Parent | on HN ]

Re:Substack's UI and 1Password temporarily cost me $2k by IncRnd on Tuesday March 23, 2021 @05:53PM (#26560848)

I didn't say it is a hidden form, but a hidden field.

[ Parent | on HN ]