479 karma · joined December 7, 2018
How about letting users decide to which capabilities they give permission depending on what they need? I don't want to push them to download and install a whole software package locally which has usually access to more data and hardware APIs compared to a webapp that temporarily lives in a browser tab.
You can see them returning no results for "tank man" from the web archive: https://news.ycombinator.com/item?id=27398376
Any reason behind your preference? It baffles me to hear you'd rather use a heavily censored and CCP-controlled search provider than a search provider from a free market with an alternative business model.
> Works fine for me
Not on June 4th[2] (the date when the Tiananmen Square massacre ended). Microsoft "fixed" it after the backlash.
Sad to see SE contributors are compared with FB users.
I do create B2B apps. Last time I had to support IE11 was 6 years ago.
[0]: https://blogs.sap.com/2021/02/02/internet-explorer-11-will-n... [1]: https://www.sap.com/why-sap.html
PWA is a set of modern web standards. "Supporting PWA" can mean many things but "Removing unfinished SSB" doesn't mean "Removing PWA".
> As mentioned, the seven-day cap on script-writable storage is gated on "after seven days of Safari use without user interaction on the site." That is the case in Safari. Web applications added to the home screen are not part of Safari and thus have their own counter of days of use. Their days of use will match actual use of the web application which resets the timer. We do not expect the first-party in such a web application to have its website data deleted. If your web application does experience website data deletion, please let us know since we would consider it a serious bug. It is not the intention of Intelligent Tracking Prevention to delete website data for first parties in web applications.
[1] https://webkit.org/blog/10218/full-third-party-cookie-blocki...
KitKat was released in 2013[1] as well as Blink in the same year[2].
Apart from Blink being a WebKit fork, WebKit itself is not "the dominant engine" anymore at least since 2014.
[0]: https://developer.chrome.com/multidevice/webview/overview