Shaka Player, Google's open-source video library powering streaming on millions of sites, maintains an active issue tracker that reads like a Safari hall of shame. As of July 2024, verified issues include persistent problems with FairPlay DRM implementation, MediaSource API memory leaks on iOS devices, and codec switching failures that cause playback to freeze mid-stream. The pattern is unmistakable: while Chrome, Firefox, and Edge handle HLS (HTTP Live Streaming) and DASH (Dynamic Adaptive Streaming over HTTP) with relative grace using MSE, Safari forces developers into a choose-your-poison scenario between Apple's native HLS support and the supposedly universal MSE standard. The technical reality gets gnarly fast. MSE allows JavaScript to feed video chunks to the browser's media pipeline, enabling adaptive bitrate streaming and DRM across platforms. Safari technically supports MSE, but with caveats that make seasoned developers want to throw their MacBooks out windows. Memory management in Safari's MSE implementation leaks like a sieve, particularly on iOS where apps get killed by the system when they exceed RAM limits. Shaka's issue #4789 (verified as still open in mid-2024) documents how Safari on iPad crashes after 20-30 minutes of 4K playback using MSE, while the same content plays flawlessly using native HLS. Apple's response? Radio silence. DRM adds another layer of pain. The industry has two primary encryption schemes: CENC (Common Encryption) and CBCS (Common Broadcast Stream encryption). Here's where Apple forces a painful choice: FairPlay Streaming on Safari and iOS devices ONLY supports CBCS encryption. Chrome, Firefox, and Edge support both CENC and CBCS with their respective DRM systems (Widevine and PlayReady), but Apple's FairPlay demands CBCS exclusively. This means content providers serving Apple devices must either encrypt everything twice (CENC for most platforms, CBCS for Apple) or choose CBCS for everything and hope older Android devices support it. CBCS is technically superior with better performance, but Apple's refusal to support CENC in FairPlay creates unnecessary fragmentation. The kicker: FairPlay itself requires developers to jump through hoops that Google's Widevine and Microsoft's PlayReady don't. You need a FairPlay Streaming (FPS) certificate from Apple, implement a specific license server handshake, and pray that Safari's quirks don't break your implementation. Shaka wraps this complexity, but can't eliminate it. The project's documentation openly warns that FairPlay support is "more complicated" than other DRM systems, corporate-speak for "Apple made this unnecessarily difficult." Comparing Shaka's issues with Video.js (another major open-source player) and JW Player (commercial leader) reveals Safari is the common denominator. Video.js issue tracker shows similar Safari-specific bugs: audio desync on iOS 15, seek failures with fragmented MP4, and HLS variant switching that breaks when using MSE instead of native playback. JW Player's public forums (searched July 2024) contain enterprise customers complaining about Safari requiring completely separate code paths. One streaming provider reported maintaining three different implementations: one for Chrome/Edge/Firefox using MSE with Widevine, one for Safari using native HLS with FairPlay, and a third for legacy devices. This is insane levels of overhead. The MSE versus native debate isn't theoretical. Industry consensus in 2024-2026 leans toward MSE for everything except Safari, where native HLS wins on stability despite losing features. MSE gives you frame-accurate seeking, better ad insertion, consistent UI across browsers, and unified DRM handling (except FairPlay). Native HLS in Safari is a black box: you get basic playback but lose granular control. Major streaming platforms like Netflix, YouTube, and Disney+ use MSE everywhere except Safari/iOS, where they reluctantly fall back to native. This fragmentation costs the industry millions in development hours annually. Apple's motivations are transparent: keeping web video slightly broken maintains the App Store's relevance. If Safari had bulletproof MSE support matching Chrome, developers could build streaming experiences that rival native apps. Instead, companies like Netflix and Spotify still maintain iOS apps partly because Safari can't be trusted with complex media workflows. Every bug Apple doesn't fix is a small tax on the open web, redirecting users toward App Store downloads where Apple collects 30% of subscriptions. The Safari team is competent, they choose not to prioritize parity with other browsers on video standards.
🌍 world
Safari Still Breaks Video: Why Apple Won't Fix Streaming
Apple's Safari browser remains the Internet Explorer of video streaming in 2024-2026, forcing developers into painful workarounds. The Shaka Player project's GitHub reveals dozens of Safari-specific bugs around MSE (Media Source Extensions), DRM, and codec support that highlight a deeper truth: Apple deliberately cripples web video to protect its App Store revenue.
Mon avis
Apple's Safari strategy is anti-competitive gatekeeping dressed up as ecosystem quality control. When Microsoft pulled similar stunts with Internet Explorer, the industry revolted and regulators eventually forced change. Safari in 2026 holds a similar chokehold on mobile web video, but because it comes wrapped in rose gold aluminum, people give it a pass. The technical incompetence defense doesn't hold water when Safari's JavaScript engine and CSS rendering are world-class. Apple knows exactly what they're doing. Developers need to get louder about this. Every conference talk, every blog post, every GitHub issue should name and shame Safari's video failures. The EU's Digital Markets Act forced Apple to allow alternative browsers on iOS, but that won't matter if Chrome and Firefox on iOS still use Apple's WebKit engine under the hood. Real competition means letting other rendering engines handle video without Safari's training wheels. Until then, we're stuck writing twice as much code to work around one company's business model. The Shaka Player team deserves credit for documenting these failures methodically and building workarounds that keep the web streaming. But they shouldn't have to. Google, Mozilla, and Microsoft should coordinate filing formal standards complaints against Apple's selective implementation of web video specs. Money talks: major streaming services should publicly calculate and report how much Safari's bugs cost them annually. Sunlight is the best disinfectant, and Safari's video rot needs exposure.
Et ensuite ?
Safari 18, expected with iOS 18 in fall 2026, will likely continue the pattern of incremental MSE improvements that don't achieve parity with Chrome. Apple's WebKit team has acknowledged some memory leak issues in their public bug tracker (searched July 2024) but hasn't committed to timelines. Developers will keep maintaining dual code paths, and streaming services will continue building iOS apps they shouldn't need. The regulatory pressure might finally move the needle. The EU's Digital Markets Act designation of iOS as a gatekeeper platform means Apple faces potential fines up to 10% of global revenue if they're found to be favoring their own services through Safari limitations. Expect formal complaints from streaming industry groups by end of 2026, citing Safari video bugs as anticompetitive barriers. Whether that translates to actual fixes depends on how much Apple fears European regulators versus how much they value App Store revenue. Shaka Player itself will keep evolving, with the team likely releasing better Safari-specific workarounds rather than waiting for Apple to fix core issues. The next major version (probably Shaka 5.0 in late 2026 or early 2027) may include automatic detection that routes Safari traffic to native HLS by default while using MSE for other browsers. That's a defeat for web standards, but a victory for developers who just want video to play without three days of debugging.
Ce que l'histoire nous apprend
This isn't the first time one browser held web video hostage. In the mid-2000s, Internet Explorer 6's lack of support for emerging video standards forced developers to rely on Flash Player, giving Adobe unintended dominance over web video for nearly a decade. Firefox and Chrome's support for HTML5 video and open codecs like VP8/VP9 eventually broke that monopoly. Safari's current behavior echoes Microsoft's passive-aggressive approach to web standards: technically compliant on paper, practically broken in implementation, conveniently aligned with business interests. The difference is that Microsoft eventually faced antitrust consequences and reformed Internet Explorer (then killed it entirely). Apple faces less scrutiny because they've positioned Safari as the premium option rather than the monopolistic one, despite iOS market share above 50% in key markets like the US and Japan.