Overpass Experiences

The Eric Wroolie Blog

  • Facebook
  • Google+
  • Linkedin
  • Twitter
  • YouTube
  • Blog
  • Social Activity
  • Videos
  • Overpass Apps

Powered by Overpass Apps

HTML5, it’s DHTML all over again

May 26, 2011 by wroolie Leave a Comment

I watched a video from MIX 2011 called “HTML5 for Silverlight Developers” last night and it was very compelling.  I was all on-board.  I would prefer to not code things in Silverlight and give my clients the caveat—“but it won’t work on an iPad”.  So, I whipped out Visual Studio and started to code.

There is something very cool about being able to code something and not have to wonder if they client has Silverlight installed.  This was awesome.

Except . . . nothing works in a browser below IE9 or Chrome or Firefox or whatever.  IE6 through IE8 didn’t work at all.

I myself am a Chrome user and gave up IE long ago unless a contract requires that I use it. But most corporate environments are a long way from upgrading to IE 8, let alone the latest IE9.

After doing some googling, I found the HTML5 shim which allows things to render properly in IE and the ExplorerCanvas javascript plugin to allow using the canvas in IE.  So, there are work-arounds.  However, these plugins allowed me to do basic things in IE8—but failed in other areas.  For example, with these plugins I could draw a rectangle on the canvas in IE8—but I couldn’t implement the drag/drop interface.

At one point, I had 5 different browsers open and was refreshing each one after making a change to my html.  Ever time, at least one of them failed.  If I tried to cater for a quirk in IE, Chrome would stop working.  When I got it working in Chrome, IE would give an ugly javascript error.

But this is nothing new.

Back in 1999, I bought an big Microsoft book called “Dynamic HTML” which espoused DHTML as the future of the web.  It gave loads of examples on how to create animations and include very cool stuff in your pages.  DHTML was term used by Netscape and IE, but this book focused entirely on Internet Explorer.  When you tried to run your same code in the counterpart Netscape browsers, nothing rendered at all and you ended up with javascript errors.  The book got around the cross-browser difficulties by ignoring all other browsers.  If you worked in a corporate environment and would never code on anything but Internet Explorer, DHTML (or the Microsoft version of it) was great.

DHTML was a broad term (as is HTML 5) and doesn’t belong to company.  You code to a certain specification and each browser (or device) renders that as they see fit.  You have very little control over how it will look unless you code with a plugin like Flash (and now, Silverlight).

I have seen fantastic DHTML animations in IE which only worked in IE.  I can remember seeing stunning animations in Netscape which didn’t work in IE (all using ‘layer’ tags).  I remember last year seeing a cool Arcade Fire video in HTML 5 which worked great in Chrome but not in IE.  There is still no consistency here.

The “HTML5 for Silverlight developers” video was a lot like the DHTML book.  It looks great until you dig deeper.

The reason I’m hesitant to jump on the HTML5 bandwagon (and I reeeallly want to) is Internet Explorers slow adoption of it.  Actually, it’s not Internet Explorer—since they are implementing a lot of new features in IE9, but most corporate environments won’t take up the new browser for at least one or two years.  So, if you put something on the web, you have to think about the large amount of lunchtime surfers who won’t even be able to see your page.  You need to write loads of conditional code just to make sure your down-level browsers can even see a message saying “Not supported by your browser” instead of a javascript “Errors in page” popup.

One thing you should never ask your clients is “What browser versions do you want this to support?”  The answer is always the same—“Well, all of them.”  This is why the IE-only inventions of the past (HTML+Time, background filters, etc) never took off.  This is why a lot of the HTML5 features—as cool as they are—won’t take off either.  We Chrome users don’t carry enough weight yet to move the entire world to the newer code.  If Apple had allowed Flash on the iPad, I don’t think anyone would care about HTML5 at all.

I want to be converted and go back to plug-in-less web development. But so far, HTML5 (or rather, the browser creators) have let us down.

Filed Under: Software Dev & Productivity

Loading Facebook Comments ...

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Preferring to Be Alone
  • How to Kill Someone’s Dreams
  • Are any Puzzle Pieces Missing?
  • Software Development Skills like Currency – And the value is always falling
  • Delegating and Giving up Control

RSS From the Overpass Blog

  • Since Apple Business Manager, Enterprise Apps Are Difficult September 11, 2019
  • Connecting Students Through School Mobile Apps May 14, 2019
  • Can You Make Money with Business Apps? April 5, 2019
  • Is an iPad App Developer the same as an iPhone Developer? February 21, 2019
  • How Apple IOS Developers need to think differently February 13, 2019
  • The Do’s and Don’ts of Enterprise Mobile App Development February 11, 2019
  • Premier mobile app development company expanding its market reach February 1, 2019
  • Overpass Apps is making waves in iOS and Android designs in the UK January 30, 2019
  • Construction Apps From Top UK Construction Companies June 7, 2018
  • Infographic: Top 5 Apps with 1 Billion Downloads June 5, 2018

Tags

Anti-virus Army Days ASP.Net Automation Baseball Beijing BR China Chinglish coding Cornbury CSS DLI Eric Wroolie Family Gym Holiday HTML5 IE6 Line Break Misc. music MVC Framework Nike+ Overpass PNG PowerShell Redcloth Ruby Runkeeper scam Skype Spotify Superpreview Textile Transparency Webby Web Design Web Standards