41–50 of 101 posts
If apple wants to treat the web like documents, that's fine, but then don't make it suck like an app. If a page is loaded, there is NO reason to randomly reload it because iOS deems it has been too long. Maybe it's a general problem with iOS killing apps in background, I don't care, it sucks.
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'…
[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.
And some features e.g. long lived first party cookies which are used for retargeting serve no legitimate purpose except to support advertisers.
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'…
This also would of course be even nicer if you could define any browser as the "target" (e.g. compare Chrome -vs- Firefox) but then that wouldn't serve their very nice domain purchase as neatly.
Because with it, we can offer users to hold their data natively on their devices. Instead of storing everything in the cloud.
So far, I think only Chrome on the desktop supports it. Here is a nice demo:
https://googlechromelabs.github.io/text-editor/
A text editor that works just like a native application.
I guess that they are missing for good reason? Web notifications? Sparsely useful, 99% is just some clickbait website trying to feed you junk. Thanks Apple! The website look cool tho.
It seems wrong to mix and match actual accepted standards with things that only Chrome implements which are not standards. Should iOS adopt [feature] because Chrome has it, or why else is it on the list? What benefits am I missing as a user? As a mainly desktop Firefox user, any time I have a web bug my developer colleagues asks me to try Chrome instead because they only develop and test in Chrome. I would say if we…
Earlier quoted context omitted.
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.
These APIs are also much more restricted than their proprietary-ecosystem equivalent.
Overall, web apps having access to these features in Chrome are an order of magnitude safer than platform-specific apps.