Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

iOS404

ios404.com

Post reply on HN
Print view View original

31–40 of 101 posts

Re: iOS404

#31

Post by threeseed »

bouncing wrote: post #24
threeseed wrote: post #20

[flagged]

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…

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.

Re: iOS404

#32

Post by notpushkin »

K0nserv wrote: post #23

This site should really include Mozilla's position on the spec too. Google shipping some, potentially harebrained, idea in Chromium doesn't mean that Safari and Firefox MUST also ship it. There should be links to relevant entries from https://mozilla.github.io/standards-positions/ and https://webkit.org/standards-positions/ This is a good example of how the chromium monoculture hurts the web. It ends up being Google'…

You can compare with Firefox by clicking on the Chrome icon – even enable both to see only features supported by both. (I think it would be a nice default view, though.)

Re: iOS404

#33

Post by madeofpalk »

Cute. Some of these are already/soon out of date. Safari Technology Preview just shipped View Transisitions API https://webkit.org/blog/15260/release-notes-for-safari-techn...

In practice, I've never missed an API on Safari for building websites that customers ask for. I have missed Chrome dragging it's feet on CSS properties like Snap Points or backdrop-filter.

The difference in culture couldn't be any more apparent, with this website having a complete disregard for users as it's actual content is just rendered into an image, not available to basic web browser functionality like copy and paste.

Re: iOS404

#34

Post by easton »

bouncing wrote: post #24
threeseed wrote: post #20

[flagged]

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…

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.

Re: iOS404

#35

Post by K0nserv »

notpushkin wrote: post #32
K0nserv wrote: post #23

This site should really include Mozilla's position on the spec too. Google shipping some, potentially harebrained, idea in Chromium doesn't mean that Safari and Firefox MUST also ship it. There should be links to relevant entries from https://mozilla.github.io/standards-positions/ and https://webkit.org/standards-positions/ This is a good example of how the chromium monoculture hurts the web. It ends up being Google'…

You can compare with Firefox by clicking on the Chrome icon – even enable both to see only features supported by both. (I think it would be a nice default view, though.)

Thanks! I totally missed that

Re: iOS404

#36

Post by guipsp »

threeseed wrote: post #20

[flagged]

Ah yes, the browser fingerprinting enabled by checks notes auto focusing an element?

It's OK to acknowledge that sometimes Google does good stuff.

Re: iOS404

#37

Post by RicoElectrico »

tgv wrote: post #4
isodev wrote: post #3

Looks awesome! While the visualization is cool, I hope some of these will remain "not found" indefinitely. Just because we can stick everything into a web-spec, doesn't mean we should.

Me too. Device orientation, USB, Bluetooth, vibration, they don't belong in a web app.

TBH Bluetooth is useful for Xiaomi e-paper clock-thermometers which can't be set without a Mi Home app... smh

Re: iOS404

#38

Post by [deleted] »

K0nserv wrote: post #23

This site should really include Mozilla's position on the spec too. Google shipping some, potentially harebrained, idea in Chromium doesn't mean that Safari and Firefox MUST also ship it. There should be links to relevant entries from https://mozilla.github.io/standards-positions/ and https://webkit.org/standards-positions/ This is a good example of how the chromium monoculture hurts the web. It ends up being Google'…

[deleted]

Re: iOS404

#39

Post by dariosalvi78 »

tgv wrote: post #4
isodev wrote: post #3

Looks awesome! While the visualization is cool, I hope some of these will remain "not found" indefinitely. Just because we can stick everything into a web-spec, doesn't mean we should.

Me too. Device orientation, USB, Bluetooth, vibration, they don't belong in a web app.

They absolutely do, if well implemented they are no more risk than any other API. The web can be what java wanted to be, if we don't screw it up.

Re: iOS404

#40

Post by madeofpalk »

agust wrote: post #12
tgv wrote: post #4

Earlier quoted context omitted.

Me too. Device orientation, USB, Bluetooth, vibration, they don't belong in a web app.

Why would they belong in a platform-specific app but not in a standard-based web app? Because Apple can't get 30% out of it?

The web lacks intentionality that installed 'native' apps have. You search for a recipie and land on a random blog, executing untrustable code from a countless number of third parties, clicking "I agree" on that modal that says "LiveLaughLove blog and out 1382 partners value your privacy".

Native apps have a much higher level of friction at multiple points that helps balance the higher level of access they get.

Post reply on HN