Live data from Hacker News

Issue 914451: Autofill does not respect autocomplete="off"

bugs.chromium.org

261–270 of 383 posts

Re: Issue 914451: Autofill does not respect autocomplete="off"

#261
post #45

Earlier quoted context omitted.

Chargeback.

Is that allowed given that you appear to have authorized it and they have proof (it's obviously not fraud or something like that)?

Most credit card companies it would be no problem at all. It shouldn’t be necessary though, a quick call to the merchant should be all that is necessary for them to void it.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#262

Earlier quoted context omitted.

Google rejecting Microsoft changes has not yet been observed, it could happen. Most people think that Google agenda could conflict with Microsoft agendas. I have read a LOT of chromium issues. I can tell you that the higher management at Google does not dictate chromium changes as they are too technical for them. The truth is, except for maybe a few exceptions, chromium evolve through the decisions of engineers that…

>I can tell you that the higher management at Google does not dictate chromium changes as they are too technical for them. Tell that to the webRequest API that ablockers use. >As you said for the exceptions, Microsoft can maintain a fork, it's still order of magnitude more economic and smart than to constantly duplicate work in a redundant browser (firefox) Chrome is the redundant browser. Firefox was here first.

webRequest API Well maybe it's an exception, but they have technical reasons mostly. Webrequest v3 is not stable so wait and see.

Chrome is the redundant browser. Firefox was here first. Well Chrome is based on khtml which is not that new but yeah Netscape navigator precede it. Indeed it would have been better if chrome was based on gecko (FF) at the time. But now Firefox can be thought of the redundant browser because of both marketshare and being technically an inferior product on most metrics.

If mozilla worked on improving chromium, think of the massive progress it would bring to the World! Website would have no limits on what is possible to create. Everything would be fast, etc.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#263
post #116

Earlier quoted context omitted.

There are no semantics to discuss. Chrome is spec compliant. That's a fact. Words like "should" and "must" have well defined meaning that is clarified in every spec document, which I would highly advise you to read before writing any further comments and insults.

SHOULD does not equal MAY

Nobody said it does.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#264
post #226

Earlier quoted context omitted.

> That begs the question Offtopic, but no it doesn't [1]. [1] https://grammarist.com/rhetoric/begging-the-question-fallacy...

When a phrase is used the “wrong” way more often than the right way, it ceases to be wrong.

Through the sheer force of repeated ignorance we change the language?

Re: Issue 914451: Autofill does not respect autocomplete="off"

#265
post #67

As a user, Chrome's autocomplete went down the drain for me once they started to fill all fields at once. I tried to autocomplete one field and often chrome filled the other fields with unfitting data. This happened so often that I started to manually complete fields even if autocomplete was available. I still miss the good old times[tm] of single-field autocomplete... (And for the record: As a developer, I have been…

This is a bit of a missing perspective. I wouldn't even care about them not following autocomplete=off if the damn autocomplete was useful. Instead 90% of the time I'm fighting it.

They really, really need to stop trying to autocomplete entire forms, and probably not anything other than "user/password" forms. The whole 'look at this input id and match it to a bunch of categories' approach has been thoroughly debunked as useless.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#266
post #226

Earlier quoted context omitted.

When a phrase is used the “wrong” way more often than the right way, it ceases to be wrong.

Through the sheer force of repeated ignorance we change the language?

Well, that's one way it happens. The language is just the set of conventions the speakers understand. When those conventions change, through ignorance or any other reason, then the language changes. That doesn't mean you can't grumble about it as it happens, though.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#267
post #138
post #8

Earlier quoted context omitted.

It causes spec-compliant password managers to not work. Unfortunately, disabling autocomplete for password fields is an often used form of security-theatre

Here's the tricky thing and I don't have a solution that doesn't get abused. I hate that lots of bank do this but I also have a use case for password autocomplete=off. We operate in an industry where shared computer access is very common and the risk of users saving password in browser is real and too high. As I said don't know what the answer is. I definitely want someone using password manager be able to use them.…

You could, I dunno, use the tools specifically provided to disable saving passwords in environments where that's undesirable:

https://thycotic.com/company/blog/2013/09/09/securing-web-br...

Re: Issue 914451: Autofill does not respect autocomplete="off"

#268

Earlier quoted context omitted.

What about "I could care less"? Seems like that one is just always wrong.

Yeah. But people say it enough I've started mentally converting it to: "I _could_ care less (but I can't be bothered)."

which is for all intents and purposes is more insulting than not being able to care less.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#269
post #226

Earlier quoted context omitted.

When a phrase is used the “wrong” way more often than the right way, it ceases to be wrong.

Through the sheer force of repeated ignorance we change the language?

I used to really, really agree with your line of thinking, and get an almost depressing feeling that this happens. But if you sit back and think about it, a lot of our 'correct' language started off as mistakes. Mayday, Ammunition, Culprit, to name 3 of a list of likely thousands...
Post reply on HN