News for hackers. Stuff that matters.

A comment on Chrome Autofill doesn't respect autocomplete=off. Parent comment

Re:Chrome Autofill doesn't respect autocomplete=off by ddoolin on Wednesday May 19, 2021 @04:42PM (#27214199)
> I work on a health industry related web app. Our web app is used by health professionals on tablets that are shared between their team members. We have a form within our app that enables our customers (the health professionals) to set up new Clients (their patients).

> Autofill is a Privacy Violation here as it is retaining identity information about Clients when it MUST NOT.

Seems to make perfectly fine sense to me.

[ Parent | on HN ]
Re:Chrome Autofill doesn't respect autocomplete=off by nomel on Wednesday May 19, 2021 @04:44PM (#27214230)
The problem is not in the autofill, it's storing the information in the first place!
[ Parent | on HN ]
Re:Chrome Autofill doesn't respect autocomplete=off by true_religion on Wednesday May 19, 2021 @05:11PM (#27214497)
Will it store things that were placed into a field with auto fill off?
[ Parent | on HN ]
Re:Chrome Autofill doesn't respect autocomplete=off by SAI_Peregrinus on Friday May 21, 2021 @06:45AM (#27232425)
AFAIK yes, caching can do so. Even if it doesn't, autofill=off doesn't require it to not store the data, just to not fill it in. Things like session resumption can still store and refill it.
[ Parent | on HN ]
Re:Chrome Autofill doesn't respect autocomplete=off by matheusmoreira on Wednesday May 19, 2021 @04:51PM (#27214313)
The web app has no control over what information the browser is and isn't saving. Autofill can and should be disabled in the browser in that case.
[ Parent | on HN ]