fix(chrome-only): Change autocomplete from 'nope' to 'off'

[Haroenv]

Reverts #250

see also #247 and fbbed04

cc @SchmidtDawid @Braunson @sdwvit

I could replicate this updated version behaving not as expected in Chrome, but also in Safari. Going back to a value as written in the specification (off) seems like the way to go for this.

[Haroenv]

We should probably make this an option, since it's so conflicting between versions.

[coveralls]

Coverage remained the same at 88.959% when pulling 708cb5f on revert-250-patch-1 into fc9a3b4 on master.

[sdwvit]

@Haroenv totally agree.
Since chrome does not respect flag, there is only one thing you can do - generate unique hash and append it to the 'name' attribute value, effectively busting chrome autocomplete cache.

[Braunson]

I think both @Haroenv and @sdwvit both have valid solutions and we should use both. Allow a flag to define the autocomplete value but you should also use unique hashes in your attribute name (when possible).

[Haroenv]

I'll add a way to customise this after