"As for why I refuse to embed Flash, let me put it this way. I use and highly recommend ClickToFlash, which blocks all Flash content by default. Why would I publish content using a technology that I personally block by default?" Soon you will be blocking and by default too, for the same reasons.
Why the HTML5 ‘Video’ Element Is Effectively Unusable
31–40 of 80 posts
Re: Why the HTML5 ‘Video’ Element Is Effectively Unusable
#32Earlier quoted context omitted.
You know, times has changed recently. Now we have not only web sites, but the web apps too. And there different rules apply.
Yes, and the vast majority of web apps boil down to forms with some flashy bits added. I'm not saying the flashy bits aren't nice, but you should build your forms in such a way that they still work without Javascript. Like I said, Google Maps is my yardstick - anything less complicated than that should be built to work without Javascript. It might work slightly different and be a little less pretty, but there's no re…
Re: Why the HTML5 ‘Video’ Element Is Effectively Unusable
#33"As for why I refuse to embed Flash, let me put it this way. I use and highly recommend ClickToFlash, which blocks all Flash content by default. Why would I publish content using a technology that I personally block by default?" Soon you will be blocking and by default too, for the same reasons.
It's not the video and audio aspects of flash he is concerned about, it's the automatic loading and playing of content with flash that is annoying. Audio and video that doesn't load until you ask for it is perfectly acceptable.
Re: Why the HTML5 ‘Video’ Element Is Effectively Unusable
#34"As for why I refuse to embed Flash, let me put it this way. I use and highly recommend ClickToFlash, which blocks all Flash content by default. Why would I publish content using a technology that I personally block by default?" Soon you will be blocking and by default too, for the same reasons.
It's not the video and audio aspects of flash he is concerned about, it's the automatic loading and playing of content with flash that is annoying. Audio and video that doesn't load until you ask for it is perfectly acceptable.
Re: Why the HTML5 ‘Video’ Element Is Effectively Unusable
#35Earlier quoted context omitted.
I am sorry but that is insane. Today's web relies heavily on JavaScript. I recommend you get yourself a clean browser (maybe on a virtual machine), if you are paranoid about security (SecurityMatters huh?), and try using Google Maps, Google Calendar, et al.
Turning off Javascript is not insane. JS opens you up to a wide range of possible security problems. Also, you can think of it ideologically - websites should still work with JS turned off. Building an accessible, semantic, well-formed website means building a website that works without Javascript. The only exceptions are Google Maps or anything equally as rich. And I do mean equally as rich.
Re: Why the HTML5 ‘Video’ Element Is Effectively Unusable
#36Earlier quoted context omitted.
Yes, and the vast majority of web apps boil down to forms with some flashy bits added. I'm not saying the flashy bits aren't nice, but you should build your forms in such a way that they still work without Javascript. Like I said, Google Maps is my yardstick - anything less complicated than that should be built to work without Javascript. It might work slightly different and be a little less pretty, but there's no re…
Google Maps is of course less interactive and shiny but still works fine without js. I'm dismayed that we don't routinely expect all web developers to be similarly talented and thorough. http://maps.google.com/maps?f=q&source=s_q&output=ht...
Re: Why the HTML5 ‘Video’ Element Is Effectively Unusable
#37Earlier quoted context omitted.
Yes, and the vast majority of web apps boil down to forms with some flashy bits added. I'm not saying the flashy bits aren't nice, but you should build your forms in such a way that they still work without Javascript. Like I said, Google Maps is my yardstick - anything less complicated than that should be built to work without Javascript. It might work slightly different and be a little less pretty, but there's no re…
Google Maps is of course less interactive and shiny but still works fine without js. I'm dismayed that we don't routinely expect all web developers to be similarly talented and thorough. http://maps.google.com/maps?f=q&source=s_q&output=ht...
Re: Why the HTML5 ‘Video’ Element Is Effectively Unusable
#38Earlier quoted context omitted.
Google Maps is of course less interactive and shiny but still works fine without js. I'm dismayed that we don't routinely expect all web developers to be similarly talented and thorough. http://maps.google.com/maps?f=q&source=s_q&output=ht...
Interestingly, a while ago I had an application where JavaScript was added later on in the game. The result was that we could split into two apps: a rich fast glitzy one and a basic one suitable for mobile devices.
I read an interesting analogy in an article (which I have since lost and so cannot give credit) about accessibility: Oxo, the kitchen tools company, started by designing tools for people with arthritis. Having designed tools with nice soft rubber grips and large handles, they discovered that non-arthritic people really liked the tools as well, and now Oxo is sold at your local Target (and they are probably raking in cash).
Re: Why the HTML5 ‘Video’ Element Is Effectively Unusable
#39That is a problem, but it seems like it would be very easy to move the image - click for video behavior into a pretty small JS library. Writing something like this probably wouldn't be all that terrible: $(function() { $('#video_1').to_video('myvideo.mp4', 'myvideo.ogg'); }); I'd still rather do that than deal with Flash.
But see that's kinda stinky cos it's not semantic. You're not embedding the video element in the document so it can describe the content. It would be really cool if the js somehow could remove the video element or something and add it back in... but I dunno how possible that is.
Re: Why the HTML5 ‘Video’ Element Is Effectively Unusable
#40Earlier quoted context omitted.
How can Firefox distribute the H.264 codecs without infringing on patents?
How do Linux distributions distribute H.264 and AAC decoders? Debian does, Ubuntu does, Fedora does, basically everything in the world except GNUsense does--yet they do just fine with themselves. The best solution would be to simply use system decoders, like Safari does. On Windows, this would be Directshow, on Linux this would be Gstreamer, and on OS X this would be Quicktime. The browser should have ABSOLUTELY NOTH…
They do not. For Debian and Ubuntu, it is in Multiverse (non-free) repositories. For Fedora, it in RPM Fusion repository. In other words, there is no distribution that distributes H.264 or AAC, so system decoders would not help at all.