3 ms·
That's the main issue. The user base for it will be relatively small for several years. Hopefully many of the people on IE 6 will leapfrog to a HTML 5 browser
by waterlesscloud 17y ago
That's the main issue. The user base for it will be relatively small for several years.
Hopefully many of the people on IE 6 will leapfrog to a HTML 5 browser in the next few years, that would solve a lot of issues.
- mark_h 17y agoMy gut feeling is that the mobile arena might be where html5 takes off first, with the number of webkit-based browsers out there now (iphone, android).
- drhowarddrfine 17y agoHow does that affect you? Your HTML markup will work in HTML5, too. In any case, I keep reading no one will use it for years yet most of the leading developers and designers I know are using it today. And I'm joining them since all my markup is now HTML5 as of six months ago.
- brlewis 17y agoThat's interesting. Can you fill out your profile with sites you've worked on?
- drhowarddrfine 17y agoBecause I speak my mind, and the truth that many don't wish to hear, I won't do that even though I'd like to.
- jacobolus 17y agoWhen you say that your markup is HTML5, do you just mean that you changed the doctype at the top (That's trivial, and its only real effect is saving a few bytes, though I suppose it's a nice symbolic gesture), or that you are now using all of the new semantic elements like <article> and <section> and <footer>, using <video> instead of plugin-based video, including features like drag-and-drop, or offline use of data-heavy apps, &c. &c.?
- drhowarddrfine 17y agoYes, using the newer elements. Haven't had a need for the others yet.