- #DOWNLOAD HTML5 VIDEO FIREFOX ADDON INSTALL#
- #DOWNLOAD HTML5 VIDEO FIREFOX ADDON UPDATE#
- #DOWNLOAD HTML5 VIDEO FIREFOX ADDON CODE#
- #DOWNLOAD HTML5 VIDEO FIREFOX ADDON DOWNLOAD#
- #DOWNLOAD HTML5 VIDEO FIREFOX ADDON FREE#
(I know, there are other applications that encourage or even require this, but that’s a Very Bad Things and Needs To Stop, and security-minded applications like Firefox absolutely should not be contributing to the problem.)
#DOWNLOAD HTML5 VIDEO FIREFOX ADDON INSTALL#
I don’t think it’s sane to assume that the end user necessarily has permissions to install software at the OS level, and I don’t think it’s good to encourage systems to be set up that way. > start playing the video via DirectX as normal. > Theora and Vorbis codecs, install them at OS level, and then
#DOWNLOAD HTML5 VIDEO FIREFOX ADDON DOWNLOAD#
> If the user said yes, Firefox would go away, download DirectX
> (ideally) say something like “I can’t play this – get codec?”. > So if a Windows user came across an Theora file, Firefox would I can’t even imagine trying to use a web browser from five years ago on today’s web, let alone fifteen! Sheesh, twenty years is a veritable eternity on the internet. Okay, so it was less than fifteen years ago. That’s a format that was in widespread use for video back in the days of NCSA Mosaic, when Yahoo was on akebono for crying out loud. Isn’t MPEG out of patent protection *yet*? Man, twenty years is *forever* in internet time. If we can reliably use a element (maybe even when JavaScript is disabled) that would fallback transparently to the plugin and Java applet tests, that would be super… and if they don’t have _any_ support, then prompting them for a Theora download would be great.īut given a choice between prompting the end-user to download something (Theora plugin) and *not* (Java applet if they have Java already), I’d rather avoid the prompt. The question for cases like ours tends to be, how can we attempt several alternate methods transparently without triggering “download this plugin!” or “download this codec!” dialogs.
#DOWNLOAD HTML5 VIDEO FIREFOX ADDON UPDATE#
* element (from back when the HTML 5 drafts required Theora… ahh those were the days! We’ll have to update it to specify the codec I guess.) * Plugin supporting application/ogg via or
I was a little dubious about the codecs (fallbacks for *mime types* have been around for ages, which doesn’t help when you might have one of a million whizz-bang codecs in the same container format), but was pleased to see that, indeed, they’ve extended the media type with a ‘codec’ option for this purpose: Īt Wikipedia & Wikimedia Commons, we’ve standardized on Ogg Theora+Vorbis for videos, and have a rather scary little system for inline playback which attempts to detect possible playback support via: > 2) the spec allows for multiple formats in the tag
> 1) The markup can list the codec required for each stream This entry was posted in Mozilla by gerv. Do any of you? Or do you know anyone who cares about web video interoperability who does?
#DOWNLOAD HTML5 VIDEO FIREFOX ADDON CODE#
Chris Double (the guy) told me he liked the idea, but didn’t have time to code it. This would be a great aid to smoothing the user experience for all sorts of video on the web, and helping content authors publish without worrying too much that some people couldn’t play their format. There are trickier issues with binary compatibility here, but perhaps they could be overcome if the data in the codec finder service were well-maintained. Similarly, if a Linux user came across an MPEG4 file, a similar thing could happen (if the necessary licensing agreements were in place). As a side-effect, players like Windows Media Player would also gain the ability to play Theora, because it uses DirectX too. If the user said yes, Firefox would go away, download DirectX Theora and Vorbis codecs, install them at OS level, and then start playing the video via DirectX as normal. So if a Windows user came across an Theora file, Firefox would (ideally) say something like “I can’t play this – get codec?”. Like the plugin finder, when it encountered media using a codec which it could not read, it would ask a codec finder service if a codec was available, but then instead of installing a browser-specific plugin it would install the codec at OS level. So a Firefox codec downloader might be a good addition to core Firefox.
#DOWNLOAD HTML5 VIDEO FIREFOX ADDON FREE#
There are very few or no formats that Windows, Mac and free Linux all can and do support. This decision has certain implications for cross-OS web video interoperability. It looks like the implementation of HTML5 in Firefox will use the native system media framework (DirectX, QuickTime, GStreamer) rather than come with any built-in codecs.