The landscape of video on the Web changed, then changed back again, and web technologies have moved on. We've witnessed:
- The fall of RealPlayer
- The rise of Flash video players, as a way to turn videos into black boxes with minimal "copy protection" (cf. "YouTube downloader" in your favourite search engine)
- The rise and precipitous fall of Silverlight (with only a handful of websites, ever, or still, using it)
- And most importantly, the advent of HTML5's <video> tag
Totem's browser plugin did as good a job as it could mimicking legacy web browser plugins from other platforms, such as QuickTime or Windows Media Player (even we stopped caring about the RealPlayer mimicking).
It wasn't helped by the ill-defined Netscape Plugin APIs (NPAPI) which meant that we never knew whether we'd receive a stream for the video we were about to play, or maybe not at all, and when you request one, you'd get one automatic one and the one you requested, or whether it would download empty files. Or we couldn't tell to open in another application when clicking directly on a file. All in all, pretty dire.
We made attempts at replacing the Flash plugin for playing back videos, but the NPAPI meant that we needed to handle everything or nothing. Ideally, we'd have been able to tell the browser to use our browser plugin for websites that we could support through libquvi, and either fallback to a placeholder or the real Flash plugin for other cases. NPAPI didn't allow us to do that.
The current state of media playback in browsers on Linux is such that:
- WebKit-based players (such as GNOME's own Web), Firefox and Chrome all support HTML5 media playback (with slightly different codec support)
- The Flash plugin is only supported with Chrome's Pepper Plugin API, which Firefox will not support.
- Chrome will soon not support NPAPI plugins.
Given all this, and the facts that Totem's browser plugin will not work on Wayland (it uses XEmbed to slot into the browser UI), that its UI is pretty broken since the redesign of the main player (not unfixable, but time consuming), and that it does not work properly in GNOME's own web browser (due to bad interactions between Clutter and GL acceleration in WebKit), I think it's time to call it a day.
Good bye Totem browser plugin.
I'll miss the clever puns of your compatibility plugins (Real Player/Complex and QuickTime/NarrowSpace being the best ones). I won't miss interacting with ill-defined APIs and buggy implementations.
Thank you for all the work you did. It was certainly a wonderful plugin.
Thank you for helping us users mind-the-gap between a web with no multimedia and a web with at least something at least vaguely like a standard. Your work was really appreciated.
My FF on GNOME `just works` everywhere I go.
Good times, good times.
I have mixed feelings about the end of NPAPI that have been brewing their way into a blog post in my head.
Thanks for fighting the good fight.
So now how do I remove it from firefox?
I have FF 38. When I check if plugins are up to date, it still shows up:
Unknown Plugins Plugin Action
Totem (v. )
The Videos 3.10.1 plugin handles video and audio streams."
Internet Business Counselors: it's been removed in GNOME 3.12 and newer.
Post a Comment