discourse/app
Sam 918a0ea3a4 FIX: use autocomplete="discourse" to disable Chrome address autofill
https://stackoverflow.com/a/47822599/17174

Chrome 63 and up start ignoring `autofill="off"`

Per: https://bugs.chromium.org/p/chromium/issues/detail?id=468153#c164

> The tricky part here is that somewhere along the journey of the web autocomplete=off become a default for many form fields, without any real thought being given as to whether or not that was good for users. This doesn't mean there aren't very valid cases where you don't want the browser autofilling data (e.g. on CRM systems), but by and large, we see those as the minority cases. And as a result, we started ignoring autocomplete=off for Chrome Autofill data

So to work around this decision we now explicitly say: autocomplete="discourse"
when we don't want Chrome to randomly fill in addressed (aka. always)
2019-02-20 10:15:59 +11:00
..
assets FIX: use autocomplete="discourse" to disable Chrome address autofill 2019-02-20 10:15:59 +11:00
controllers FIX: removes legacy browsers-refresh button (#7028) 2019-02-19 16:38:21 +01:00
helpers FEATURE: Calculate sprite-sheet based on currently active themes (#6973) 2019-02-06 15:51:23 +00:00
jobs PERF: only require aws-sdk-sns gem when it's being used 2019-02-14 11:08:21 +01:00
mailers FIX: Keep original subject in emails to staged users 2019-01-18 11:07:54 +01:00
models FIX: Don't try to rename group when username is taken 2019-02-19 22:31:03 +01:00
serializers FIX: unable to create new categories 2019-02-15 10:24:29 +11:00
services FIX: Push notifications could fail with UnauthorizedRegistration 2019-02-15 21:12:09 +01:00
views PERF: Cache build_not_found_page 2019-02-12 21:20:33 +11:00