As the screenshot below shows, Firefox and Opera don't support the H.264 compression standard, so you can't play videos from sites that only use H.264. Even if video sites like YouTube or Vimeo started to test HTML5 players, they don't offer the option to embed videos using HTML5 tags.
{ via Google Reader's Twitter page. Thanks, François. }
What does that mean? I thought that audio and video tags were (or were not) supported by a given browser, not by a webapp. I thought that if a feed contains audio or video tags, as soon as you use a browser that supports them (and implements the right compression standard for the content of the feed), then you should be able to see that content, no matter the webapp you use (Google Reader, Netvibes, ...). Am I missing something here?
ReplyDelete@Alexandre:
ReplyDeleteYes, you're missing something. Google Reader is a web-based feed reader that processes feeds and filters unsafe content. For example, Google Reader removes JavaScript code, iframes and only displays Flash content from a list of trusted domains (for example: YouTube.com). Until now, video and audio tags were ignored by Google Reader, probably because not many browsers supported them.
Thank you! So, saying that Google Reader "supports" audio and video tags simply means that they added those tags to the list of "unfiltered" content from the feeds.
ReplyDelete