![]() ![]() This one is probably the one of the more common inputmode values out in the wild because it’s ideal for inputs that require numbers but no letters - things like PIN entry, zip codes, credit card numbers, etc. Regardless, none is intended for content that renders its own keyboard control. iOS 12.2 will still show its default alphanumeric keyboard, so specifying none could be sort of a reset for iOS in that regard. Using inputmode=none will not show a keyboard at all on Chrome for Android. We’re starting here because it’s very possible we don’t want any type of keyboard on an input. ![]() Given that WHATWG has documented it and browsers have worked toward supporting it, we’re going to go assume WHATWG specifications are the standard. ![]() I’ve reached out to see if we can sync up our findings.īut before we go deep into the ins and outs of the attribute, consider that the WHATWG living standard provides inputmode documentation while the W3C 5.2 spec no longer lists it in its contents, which suggests they consider it obsolete. Based on my tests, inputmode is indeed supported in Opera Mini and Opera Mobile, which contradicts the Caniuse data above. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |