It's only ~8% of the desktop market share and ~4% across all devices. It doesn't seem inconceivable sites just give up supporting it if they're not getting the ad revenue.
It's only ~8% of the desktop market share and ~4% across all devices. It doesn't seem inconceivable sites just give up supporting it if they're not getting the ad revenue.
That just means I tell my colleagues I can't receive Slack audio calls and we use an alternative tool for that.
There is momentum in a choice like that though and even if Slack were to add Firefox support tomorrow we probably wouldn't switch to using them for audio.
They do offer an election based app for Linux but I'm not interested in that over head when I can just keep a browser tab open for Slack chat.
For me you either support open standards or you don't get used.
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36
> But if Google does this properly and uses more sophisticated browser fingerprinting techniques, Epiphany is done for. This could be an existential threat for non-Safari WebKit browsers. Nobody is going to be interested in using a browser that doesn't support Google websites. Google's expressly-stated goal is to block embedded browser frameworks and non-supported browsers from signing into Google accounts. The blog post says: "This block affects CEF-based apps and other non-supported browsers." It says: "We do not allow sign-in from browsers based on frameworks like CEF or Embedded Internet Explorer."
[1] https://lists.webkit.org/pipermail/webkit-dev/2020-November/...