4 ms·

Safari is the absolute worst web browser by far. Both mobile and desktop. This kind of egregious error is only the most obvious part. Try doing a WebRTC conf

Safari is the absolute worst web browser by far. Both mobile and desktop. This kind of egregious error is only the most obvious part. Try doing a WebRTC conference call in Safari. Google Meet, Microsoft Teams, Slack, Zoom, Jitsi Meet, etc, etc, etc. None of them support Safari. Do you know why? It's because Safari is absolutely riddled with bugs: [1][2][3]. It is incredible how bad Safari is. [1] https://bugs.webkit.org/show_bug.cgi?id=211181 https://bugs.webkit.org/show_bug.cgi?id=211181 [2] https://bugs.webkit.org/show_bug.cgi?id=212669 https://bugs.webkit.org/show_bug.cgi?id=212669 [3] https://bugs.webkit.org/show_bug.cgi?id=212780 https://bugs.webkit.org/show_bug.cgi?id=212780

lern_too_spel 6y ago
I once tried to watch a video sped up in Safari, and the sound was awful. An acquaintance tried to report the bug to Apple years ago, and it went into a black hole. Compare to the public bug trackers for Firefox and Chromium, and it's easy to understand why Safari remains nearly useless.
- saagarjha 6y ago
  WebKit has a public bug tracker.
  - VWWHFSfQ 6y ago
    Apple Safari (mobile and desktop) doesn't use the WebKit.org bug tracker. They do their own thing.
    - shuckles 6y ago
      Video playback is a WebKit feature.
      - lern_too_spel 6y ago
        The platform audio libraries that Webkit uses on MacOS and iOS are not part of Webkit.
        saagarjha 6y ago
        They aren't, but WebKit does a lot of the work around that and it's possible that the bug is in that rather than the platform libraries (which generally do work outside of the browser…) I'd say it's worth filing a bug for WebKit and then see if they send you over to Safari.
coronadisaster 6y ago
It is probably done on purpose so that you use the apps instead of the browser... it's not like they don't have the money to fix it.
om2 6y ago
Google Meet works fine, as does Jitsi Meet. We're working with popular WebRTC providers one at a time. Unfortunately, the state of WebRTC interop is pretty bad across the board, so providers use website lockouts and qualify one browser at a time. Sorry about those three bugs. They do sound like bugs and will be looked into.
- hutattedonmyarm 6y ago
  Huh, I never got anything that does audio/video calling to work on Safari. Always only provides a test video and audio. Permissions are all granted
  - platypushexley 6y ago
    Isn't that the "Use mock capture devices" function in the Develop > WebRTC menu?
  - om2 6y ago
    Sounds like a bug. The things I mentioned should work, as well as bluejeans and tokbox among others. If they don't for you, please file via Feedback Assistant with a sysdiagnose.
frank2 6y ago
May I ask: do you or have you recently developed web front ends for money?
NorwegianDude 6y ago
Could not agree more, at least for iOS safari. It's way worse that IE ever was. Safari lacks features, it's inconsistent, it's full of bugs, and the worst part? There is nothing you can do about it, it's not like Apple allows other browsers access to the platform. I can't even count the number of times where scrolling stops working, but then you refresh the page and it works again, even if it's the exact same HTML and CSS. And then there was the issue hundreds of user complained about: the keyboard would not show up when pressing the url bar, on any page. Quitting and opening safari again usually fixed this. For some reason iOS users seems to have no idea what's what. When the browser stops working, they usually contact me, like I would be able to do anything about it. Apple needs to take feedback from their users.

lern_too_spel 6y ago

I once tried to watch a video sped up in Safari, and the sound was awful. An acquaintance tried to report the bug to Apple years ago, and it went into a black hole. Compare to the public bug trackers for Firefox and Chromium, and it's easy to understand why Safari remains nearly useless.

saagarjha 6y ago
WebKit has a public bug tracker.
- VWWHFSfQ 6y ago
  Apple Safari (mobile and desktop) doesn't use the WebKit.org bug tracker. They do their own thing.
  - shuckles 6y ago
    Video playback is a WebKit feature.
    - lern_too_spel 6y ago
      The platform audio libraries that Webkit uses on MacOS and iOS are not part of Webkit.
      - saagarjha 6y ago
        They aren't, but WebKit does a lot of the work around that and it's possible that the bug is in that rather than the platform libraries (which generally do work outside of the browser…) I'd say it's worth filing a bug for WebKit and then see if they send you over to Safari.

coronadisaster 6y ago

It is probably done on purpose so that you use the apps instead of the browser... it's not like they don't have the money to fix it.

om2 6y ago

Google Meet works fine, as does Jitsi Meet. We're working with popular WebRTC providers one at a time. Unfortunately, the state of WebRTC interop is pretty bad across the board, so providers use website lockouts and qualify one browser at a time. Sorry about those three bugs. They do sound like bugs and will be looked into.

hutattedonmyarm 6y ago
Huh, I never got anything that does audio/video calling to work on Safari. Always only provides a test video and audio. Permissions are all granted
- platypushexley 6y ago
  Isn't that the "Use mock capture devices" function in the Develop > WebRTC menu?
- om2 6y ago
  Sounds like a bug. The things I mentioned should work, as well as bluejeans and tokbox among others. If they don't for you, please file via Feedback Assistant with a sysdiagnose.

frank2 6y ago

May I ask: do you or have you recently developed web front ends for money?

NorwegianDude 6y ago

Could not agree more, at least for iOS safari. It's way worse that IE ever was. Safari lacks features, it's inconsistent, it's full of bugs, and the worst part? There is nothing you can do about it, it's not like Apple allows other browsers access to the platform. I can't even count the number of times where scrolling stops working, but then you refresh the page and it works again, even if it's the exact same HTML and CSS. And then there was the issue hundreds of user complained about: the keyboard would not show up when pressing the url bar, on any page. Quitting and opening safari again usually fixed this. For some reason iOS users seems to have no idea what's what. When the browser stops working, they usually contact me, like I would be able to do anything about it. Apple needs to take feedback from their users.