"Fixes and improvements in Adobe Flash Player 9 Update 3, Version 9.0.115.0
Flash Player 9 Update 3 extends the performance and standards compliance advances introduced in Flash Player 9. Of key importance, this update adds H.264 video and High Efficiency AAC (HE-AAC) audio codec support that opens up a broad ecosystem and selection of standards-based video — up to HD quality — that developers can leverage in their applications. The update also features hardware accelerated, multi-core enhanced, full-screen video playback for high-resolution viewing across major operating systems and browsers."
(my emphasis)
That's largely irrelevant to the issue at hand being just Adobe trying to grasp the last few straws of universal flash desirability before browsers offer the codecs necessary aside from Flash and Canvas becomes the standard format for online animation.
I assume Firefox has a public API for video codecs, and they choose to distribute codecs or not. So I don't see the difference, really.
They really don't and they really should. Building a plugin architecture where users could decide based on their local laws which technology to use when some may be patent encumbered would be a big win for open source, standards, and freedom on the Internet.
Because today instead of WMV/QuickTime/etc. we have H.264/H.264/Flash (which streams H.264).
I see a lot of VP6 and Sorenson listed there. What we really have today is Flash/Flash/Flash. I'm curious about how much VC-1 use there is in the wild in the large Microsoft/Silverlight streaming video installations.
This is most definitely false. Why make a claim like this when you could easily verify it?
Firefox (at least on Windows) has a special Flash installer baked into it for several years -- if it can't find the plugin, it prompts you with an infobar, which then kicks off a streamlined installer that downloads a xpi package and installs it even without administrative privileges.
When they first implemented it, they got a special license to distribute the Flash xpi from addons.mozilla.org, and did so happily. Mozilla has absolutely distributed the Flash binaries themselves before, but I think the file is hosted by Adobe these days.
Fairly recently they baked in a special Flash updater too -- if your Flash plugin has known security vulnerabilities Firefox will prompt you to automatically update it: http://blog.mozilla.com/metrics/2009/09/16/helping-people-up...
The "special Flash updater" detects if the user has Flash installed and is out of date, and only if so, it points them to Adobe's website to download the latest version. This is likely to happen for all widely used plugins. Flash is the first because it's so widely installed. More details here: http://blog.mozilla.com/security/2009/09/04/helping-users-ke...
It's pretty easy to find this all out with a search engine, so I'm beginning to wonder if your "slightly incorrect" claims are deliberate misrepresentations. I'd question your agenda, but honestly I don't care. The facts are available for anybody with a search engine handy.
Gnash and swfdec are available via Debian and Ubuntu's independent PFS servers as an xpi in their Mozilla forks, but not through Mozilla normally since I don't think their UI will present multiple options for one set of <embed> attributes.
The feature exists solely because Flash doesn't ship in the default installs of Windows (or in OEM installs in NPAPI form), or any of the Linux distros (just OS X).
Mozilla are collaborators: they don't have the moral high ground here.
Mr. Gruber should be more precise by what he means by support.
Firefox's support for Flash is not like the proposed support for H.264. There is no Flash code in the Firefox codebase, to my knowledge. There is only a generic plugin interface, and there is one dominant, proprietary Flash plugin that Mozilla has nothing to do with (in addition to other less-featured Flash plugins).
What Mr. Gruber seems to be saying is that he wants Firefox to distribute H.264 code with their browser. Either that or Firefox should rely on codecs that may or may not be installed on the underlying system.
In the former case, the analogy is fatally flawed, while if the latter is intended, it should be explicitly addressed.