Hacker News Reader

Comment by IncRnd | Hacker News Reader

Ths is an appeal to authority. It is a shortcoming of the product's design for it to autofill a hidden field.

It is a visible input field styled not to look like an input field until that radio button is selected, but it is not "hidden" in the HTML sense. It is not a shortcoming of the product's design to not have parsed the CSS and intuited that Substack's designers wanted to cleverly make it not look like an input field.

> It is not a shortcoming of the product's design to not have parsed the CSS and intuited that Substack's designers wanted to cleverly make it not look like an input field.

How is it not a shortcoming? Any human looking at the page can immediately tell that this form field should not be autofilled.

Difficult problem to solve? Sure, doesn't make it any less of a shortcoming.

It’s visually hidden for us to see, not for 1Password auto fill mechanism.

Which is a problem in the 1Password autofill mechanism. Unless you believe that it should be filling forms which are hidden from humans?

So you want 1Password to check CSS of the form before auto filling? The form itself isn’t hidden it’s styled to be flat. That’s the biggest problem of it.

That exactly correct, which is why the fault is with 1Password's fill mechanism.

A product has a bug when it does not produce output in-line with its stated purpose and process. Nobody would use a refrigerator that suddenly forgets to keep food cold when a carton of milk is placed on the shelf.

Reply on news.ycombinator.com