This repository was archived by the owner on Oct 29, 2020. It is now read-only.
Attempt to disbale autocomplete.#2624
Merged
weerd merged 1 commit intoDoSomethingArchive:devfrom Jun 20, 2014
weerd:sms-campaign--autocomplete
Merged
Attempt to disbale autocomplete.#2624weerd merged 1 commit intoDoSomethingArchive:devfrom weerd:sms-campaign--autocomplete
weerd merged 1 commit intoDoSomethingArchive:devfrom
weerd:sms-campaign--autocomplete
Conversation
Contributor
|
🏁 |
Contributor
|
Sure 🎱 👍 |
Contributor
Author
|
huzzah! let's give it a whirl. |
weerd
added a commit
that referenced
this pull request
Jun 20, 2014
Attempt to disbale autocomplete.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Not 100% this will work to eliminate the autofilling of the multiple phone number fields we saw during user testing. This approach could work, but it's dependent on the browser actually paying attention to this attribute on the
<input>.This seems to be a very browser specific and OS specific issue which is harder to address universally.
Resolves #2460
@DFurnes @aaronschachter