News for hackers. Stuff that matters.
Re:“autocomplete=off is ignored on non-login input elements” by gkya on Wednesday June 15, 2016 @05:04PM (#11912131)
> There's very few occasions when autocomplete being disabled makes sense

What are those (seriously, I can't think of any off the top of my head).

Re:“autocomplete=off is ignored on non-login input elements” by chillacy on Wednesday June 15, 2016 @05:25PM (#11912256)
I know of one from a previous project. We had a prompt that said "enter your home address" with JavaScript autocomplete using google location APIs. Unfortunately chrome would try to auto fill this box with a city name (not even the full address) and this auto fill prompt sat on top of the JS drop down.
Re:“autocomplete=off is ignored on non-login input elements” by gkya on Wednesday June 15, 2016 @07:17PM (#11912840)
Wouldn't making it a textarea w/ rows=1 work? AFAIK textarea is not completed.
Re:“autocomplete=off is ignored on non-login input elements” by kalleboo on Wednesday June 15, 2016 @08:59PM (#11913291)
So we're back to hacks to replicate a feature that browser developers have decided to ignore? Gotta love web technology.

If "just use a textarea" is a valid solution, why did Google even bother not honoring autocomplete?

Re:“autocomplete=off is ignored on non-login input elements” by gkya on Wednesday June 15, 2016 @09:28PM (#11913390)
Well, the web technology is a pile of sh.t and in this case with the textarea you don't put your hands as deep in to is as you'd with the text input. That's how I interact with the web technology.
Re:“autocomplete=off is ignored on non-login input elements” by kalleboo on Wednesday June 15, 2016 @10:06PM (#11913498)
It's just amusing, that's all.

Prediction for the future:

1. Google implements auto-complete for one-line textareas

2. Web developers create textareas with 2 lines but hide the bottom line with CSS and disable the return key

3. Something so diabolical even I can't think of it

Re:“autocomplete=off is ignored on non-login input elements” by chillacy on Thursday June 16, 2016 @02:07AM (#11914325)
Yea that's a good idea. I don't like it because it's hacky, but if that's the only option... ¯\_(ツ)_/¯
Re:“autocomplete=off is ignored on non-login input elements” by ori_b on Thursday June 16, 2016 @12:34PM (#11917200)
That's a bug in autocompletion -- if it had autofilled correctly, with the full address -- there would be no discussion here.

If autocompletion had worked as intended, everyone would be happier than if it was disabled.

Re:“autocomplete=off is ignored on non-login input elements” by MikeTV on Wednesday June 15, 2016 @05:31PM (#11912300)
In our user management portal, whenever tech support opens the Create New User or Reset User Password page Chrome helpfully fills their administrative password into the user's password field.
Re:“autocomplete=off is ignored on non-login input elements” by gkya on Wednesday June 15, 2016 @07:16PM (#11912832)
So in your user management portal, you assign new users or replace your lost passwords with passwords you set, thus you know? Oh my days! Generate it randomly and mail the user, or better, mail them a link to reset/create password page. Otherwise, just make it a plain input field, because if you know it, it's not hidden anyways.
Re:“autocomplete=off is ignored on non-login input elements” by MikeTV on Thursday June 16, 2016 @09:38AM (#11915972)
Every hurdle vs. proper security has been non-technical. Slowly making progress :-)
Re:“autocomplete=off is ignored on non-login input elements” by IanCal on Thursday June 16, 2016 @01:05AM (#11914126)
Any search box where you want to hit a backend server and do typeahead searching.

Edit - for a good example, google use it on their search box.