4 ms·
It's sad that they don't provide context like MacOS crashes with Safari but not with Firefox or Chromium-based browsers. Would be interesting if it's actually t
by bionade24 5y ago
It's sad that they don't provide context like MacOS crashes with Safari but not with Firefox or Chromium-based browsers. Would be interesting if it's actually the UMA memleak problem reported not long ago.
Notice: I don't know if any browser besides Safari can play HDR content on MacOS.
- Uehreka 5y agoChrome on macOS is playing back HDR just fine.
- gigglesupstairs 5y agoThe linked macrumors post lists multiple responses of it happening inside chrome too.
- sudhirj 5y agoI think media playback is delegated to the OS by the browser through some API, I doubt every browser bundles its own decoding and playback engine. And it needs to handover to the OS for picture-in-picture as well, makes sense to delegate.
- rudian 5y agoI think none of what you said is necessarily true. Safari certainly delegates as much as possible, but other browsers have a lot of baggage that OSes don't necessarily support. PIP is just a floating window, they have existed without explicit OS support for decades.
- sudhirj 5y agoNot in macOS, though — PiP seems very heavily integrated into the OS, and seems to switch to OS UI when activated. Same thing happens in iOS as well.
- ksec 5y ago> I doubt every browser bundles its own decoding and playback engine. Not sure if that is the case on Mac but I am pretty sure Firefox bundle its own decoding and playback engine on Windows. And the same for Chrome. ( They are practically a mini OS ) The only one using OS default is Safari. Hence why supporting VP9 or other codec require an OS update. Unless of course it is Hardware Accelerated Decoding.