Does this apply to Dragon as well?
Due to licensing and legal reasons, probably not. Remember, Chrome is Google’s project, whereas Chromium is the community version (where we get our code from).
That’s what I figured. I just didn’t know if Comodo was going to jump on the “bandwagon”.
From a security standpoint, Adobe Flash is horrible. I doubt as a security company we would even consider it. Google is doing this because of YouTube in my opinion.
We believe this initiative will help our users in the following ways:
When users download Chrome, they will also receive the latest version of Adobe Flash Player. There will be no need to install Flash Player separately.
Users will automatically receive updates related to Flash Player using Google Chrome’s auto-update mechanism. This eliminates the need to manually download separate updates and reduces the security risk of using outdated versions.
With Adobe’s help, we plan to further protect users by extending Chrome’s “sandbox” to web pages with Flash content.
Though Flash update support is commendable it is unclear why it was not extended to other plugins (Microsoft Silverlight aside). Extending sandbox support to pages with flash content is good news considering that chromium got a far worse implementation on XP.
Whereas some changes will inevitably get into Chromium it would be nice to see Dragon feature some sort of all-round Plugin check: Indeed something preferable and unrelated to any partnership (though, accounting for flash userbase chrome will contribute to, it is easy to see some security reason in Google’s agenda)
As per informations provided in Royalty Deadline for H.264 Extended, But It’s Still Bad for the Web:
Is that the reason Dragon lacks H264 support?
From a personal (Read: non-Comodo) standpoint, I would 100% agree with that statement. I would LOVE to see YouTube (and other sites) use multiple formats. (Ogg Theora, Flash, h.264, etc.) to maintain a free and open web, but I think the market saturation behind h.264 is so ginormous that we’ll be FORCED into another proprietary format instead of using a Free and OPEN codec such as Theora. Especially since Apple and Sony are major players behind h.264 (and now Google)
Indeed it is not that end-users got much choice over content-distributors platforms and it is somewhat unsettling to see some browser/devices lacking native theora support.
It looks like html5 video support might be fragmented further in future as Google got holds of Theora VP3 legacy and its insofar less open (but more advanced) siblings
Very interesting. I was really hoping this would spark opinions and discussion. I use CD almost exclusively. This issue does matter to a lot of people.
It is time we shift over to HTML 5
I’m not quite sure you understand HTML5. The Video element of HTML supports many different video containers. It is up to the HTML5 implementer to provide a way to decode the element. (Opera makes use of gstreamer on Windows, Mac and Linux) . This is why Firefox has Theora support embedded and Chrome has h.264 support embedded
http://diveintohtml5.org/video.html (Link Courtesy of another forum member, who I forget their name)