wubin

HTML switch was already requested in 2018: https://github.com/whatwg/html/issues/4180

The change that broke the extensions is reverted for now due to the reported issues.

USB, Bluetooth [...] have no place in a browser

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.

No, we're not referring to it being blocked only in China. It was blocked on 4th June worldwide by all search engines that rely on Bing (DDG, Qwant, Ecosia, ...)

You can see them returning no results for "tank man" from the web archive: https://news.ycombinator.com/item?id=27398376

I'd honestly rather have a search provider run by the CPC

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.

DuckDuckGo, Qwant, Ecosia, Yahoo, etc. they all rely on Bing (Some only for images)[1].

Works fine for me

Not on June 4th[2] (the date when the Tiananmen Square massacre ended). Microsoft "fixed" it after the backlash.

[1] https://www.searchenginemap.com/

[2] https://news.ycombinator.com/item?id=27398376

True. I abandoned Facebook long time ago because of its low-value feed. Recently had to join LinkedIn and was disappointed immediately to see yet another feed which is rarely informative whomever I follow

You moved from WebKit to WebKit

Stack Exchange sites are not mere social media but more like an encyclopedia for specific topics. Answering as well as asking good questions requires extensive research and being mindful of future readers.

Sad to see SE contributors are compared with FB users.

I doubt MS wants that kind of segmentation if they themselves rely strongly on the Chromium project.

HN is blocked in China.

SAP, one of the largest ERP vendors, is dropping IE support this year for most of their products including legacy ones.[0] And according to SAP, "91% of Forbes Global 2000" are SAP customers.[1] So we can expect enterprises moving to "modern browsers" this year if not done already.

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

FF only removed the SSB (site specific browser) feature on desktop which was in an alpha state. There was no announcement that Mozilla was going to remove the entire PWA features (such as service workers).

PWA is a set of modern web standards. "Supporting PWA" can mean many things but "Removing unfinished SSB" doesn't mean "Removing PWA".

The main article as well as the linked post mentions that the classic Edge (EgdeHTML) is also affected. Hence "legacy browsers" in the title.

Yes, it's actively encouraged by the Theia community to align the DX to VS Code: https://youtu.be/NLkQzx6rrnU?t=1040

The source clarifies that this only applies to websites run within the Safari browser.[1] PWAs added to the home screen aren't affected.

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...

Additionally, here is a list of what browsers will be able to do:

https://goo.gle/fugu-api-tracker

Since Android 4.4 (KitKat), the WebView component is based on the Chromium open source project. (...) Webviews also share the same rendering engine as Chrome for Android. [0]

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

[1] https://en.wikipedia.org/wiki/Android_version_history

[2] https://en.wikipedia.org/wiki/Blink_(browser_engine)