4 ms·
Did “everyone” agree on and implement them, or did Google implement them and force everyone else in the WHATWG to play catch-up since they’re dominant?
by marxisttemp 2y ago
Did “everyone” agree on and implement them, or did Google implement them and force everyone else in the WHATWG to play catch-up since they’re dominant?
- do_not_redeem 2y agoMaybe there are specific examples of that? But I can't think of any, and it certainly doesn't strike me as common. Random example: https://caniuse.com/input-inputmode https://caniuse.com/input-inputmode Firefox: 2013 Chrome: 2017 Safari: Any decade now, I'm sure of it
- fingerlocks 2y agoYour own link says it’s supported on Safari for iOS, for years now. It’s obviously not supported on MacOS because that attribute only applies to onscreen keyboards.
- hu3 2y agoWhat makes you think onscreen keyboards are not useful in macOS if at least for accessibility reasons?
- fingerlocks 2y agoThe browser feature under discussion is clearly intended for small screen mobile devices. Accessibility keyboards are just keyboards from the web page’s perspective
- hu3 2y agoIt's clearly NOT intended only for small screen mobile devices. There's no reason to restrict suggesting input types to mobile browsers only. That's exactly why desktop Chrome and Firefox has support it for a long time now.
- fingerlocks 2y agowell apparently Apple disagrees
- hu3 2y agoyeah, as usual. That's exactly the point