Add autocorrect, autocapitalize, autocomplete attributes #2417

Open
eagle-r opened this Issue Apr 7, 2016 · 5 comments

Comments

Projects
None yet
5 participants
@eagle-r

eagle-r commented Apr 7, 2016

I think it would be helpful to add the above HTML5 attributes support on mobile browsers can vary widely.

@cvrebert

This comment has been minimized.

Show comment
Hide comment
@cvrebert

cvrebert Apr 10, 2016

Contributor

autocomplete is already in caniuse: http://caniuse.com/#feat=input-autocomplete-onoff

autocapitalize and autocorrect aren't part of HTML5. They're both nonstandard.

Contributor

cvrebert commented Apr 10, 2016

autocomplete is already in caniuse: http://caniuse.com/#feat=input-autocomplete-onoff

autocapitalize and autocorrect aren't part of HTML5. They're both nonstandard.

@eagle-r

This comment has been minimized.

Show comment
Hide comment
@eagle-r

eagle-r Apr 11, 2016

Ok, fair enough that they’re non-standard but they are recognised by a
number of browsers.

On Sun, Apr 10, 2016 at 4:38 PM, Chris Rebert notifications@github.com
wrote:

autocomplete is already in caniuse:
http://caniuse.com/#feat=input-autocomplete-onoff

autocapitalize
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Input#attr-autocapitalize
and autocorrect
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Input#attr-autocorrect
aren't part of HTML5. They're both nonstandard.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2417 (comment)

eagle-r commented Apr 11, 2016

Ok, fair enough that they’re non-standard but they are recognised by a
number of browsers.

On Sun, Apr 10, 2016 at 4:38 PM, Chris Rebert notifications@github.com
wrote:

autocomplete is already in caniuse:
http://caniuse.com/#feat=input-autocomplete-onoff

autocapitalize
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Input#attr-autocapitalize
and autocorrect
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Input#attr-autocorrect
aren't part of HTML5. They're both nonstandard.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2417 (comment)

@jonesiscoding

This comment has been minimized.

Show comment
Hide comment
@jonesiscoding

jonesiscoding May 5, 2016

Definitely non-standard, but as of Chrome 43 autocapitalize is supported on Android. It's been part of iOS since iOS 5. I suspect that it's honored on Yosemite/El-Capitan's versions of Safari too, but I can't test at this moment.

IOS Reference: https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariHTMLRef/Articles/Attributes.html#//apple_ref/doc/uid/TP40008058-autocapitalize

Android Reference:
https://developers.google.com/web/updates/2015/04/autocapitalize?hl=en

The fact that it's support isn't standardized or consistent cross browser would be all the more reason to have it listed.

Definitely non-standard, but as of Chrome 43 autocapitalize is supported on Android. It's been part of iOS since iOS 5. I suspect that it's honored on Yosemite/El-Capitan's versions of Safari too, but I can't test at this moment.

IOS Reference: https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariHTMLRef/Articles/Attributes.html#//apple_ref/doc/uid/TP40008058-autocapitalize

Android Reference:
https://developers.google.com/web/updates/2015/04/autocapitalize?hl=en

The fact that it's support isn't standardized or consistent cross browser would be all the more reason to have it listed.

@Schweinepriester

This comment has been minimized.

Show comment
Hide comment
@Schweinepriester

Schweinepriester Oct 9, 2016

Contributor

Imho duplicate of #1729 and #1953.

Contributor

Schweinepriester commented Oct 9, 2016

Imho duplicate of #1729 and #1953.

@cvrebert

This comment has been minimized.

Show comment
Hide comment
@cvrebert

cvrebert Jan 9, 2018

Contributor

@Fyrd Close this as a duplicate of the existing 2 issues?

Contributor

cvrebert commented Jan 9, 2018

@Fyrd Close this as a duplicate of the existing 2 issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment