3 ms·

That's more or less how HTML has always been. Before Chrome, it was IE just adding stuff. Before IE, it was Netscape just adding stuff. JavaScript itself is jus

That's more or less how HTML has always been. Before Chrome, it was IE just adding stuff. Before IE, it was Netscape just adding stuff. JavaScript itself is just a browser adding stuff. Like it or not, W3C standards have always been reactive to what browsers are already doing. And what's really remarkable about this list is that quite a few are supported on Safari on Mac, just not on iOS. Like autofocus. It's just a simple attribute you can put on an <input> tag that autofocuses that element when the page loads. It's on Mac Safari. It's on Android browsers. It's just not on any iOS browser because, you have to assume, someone at Apple held it back for not very good reasons.

actionfromafar 2y ago
Couldn't it have to do with how touch works? You always have to tap where you type anyways.
threeseed 2y ago
That doesn’t mean that we should just adopt any nonsense that Google comes up with. Also autofocus on page load is a terrible idea on iOS as it automatically brings up the keyboard. No one wants to switch between web pages and suddenly have to wait for the keyboard to appear each time on page load.
- bouncing 2y ago
  Android has handled this fine since approximately forever. It focuses the element, but doesn't necessarily bring up the keyboard until you tap it.
  - threeseed 2y ago
    Pretty poor UX. Expectation on iOS is that anything that is focused you should be able to type into.
- hasanhaja 2y ago
  > That doesn’t mean that we should just adopt any nonsense that Google comes up with. That's a fair statement. Conversely, why should we put up with Apple stifling the web platform? Especially when there's strong evidence to show this is motivated primarily by profit rather than the user experience [1][2]. [1] https://open-web-advocacy.org/walled-gardens-report/ https://open-web-advocacy.org/walled-gardens-report/ [2] https://changelog.com/jsparty/316#t=00:25:59.26 https://changelog.com/jsparty/316#t=00:25:59.26
easton 2y ago
The difference specifically for autofocus being that the keyboard will appear when that happens on iOS, whereas on your Mac the keyboard is always out regardless of focus. I can see how that would be annoying.

actionfromafar 2y ago

Couldn't it have to do with how touch works? You always have to tap where you type anyways.

threeseed 2y ago

That doesn’t mean that we should just adopt any nonsense that Google comes up with. Also autofocus on page load is a terrible idea on iOS as it automatically brings up the keyboard. No one wants to switch between web pages and suddenly have to wait for the keyboard to appear each time on page load.

bouncing 2y ago
Android has handled this fine since approximately forever. It focuses the element, but doesn't necessarily bring up the keyboard until you tap it.
- threeseed 2y ago
  Pretty poor UX. Expectation on iOS is that anything that is focused you should be able to type into.
hasanhaja 2y ago
> That doesn’t mean that we should just adopt any nonsense that Google comes up with. That's a fair statement. Conversely, why should we put up with Apple stifling the web platform? Especially when there's strong evidence to show this is motivated primarily by profit rather than the user experience [1][2]. [1] https://open-web-advocacy.org/walled-gardens-report/ https://open-web-advocacy.org/walled-gardens-report/ [2] https://changelog.com/jsparty/316#t=00:25:59.26 https://changelog.com/jsparty/316#t=00:25:59.26

easton 2y ago

The difference specifically for autofocus being that the keyboard will appear when that happens on iOS, whereas on your Mac the keyboard is always out regardless of focus. I can see how that would be annoying.