Adobe Releases HTML5 Pack for Dreamweaver CS5

| Product News

Adobe announced the immediate availability of its new HTML5 Pack for Dreamweaver CS5 at Google’s I/O event on Wednesday. The add-on pack for Dreamweaver enhances the Web design application’s HTML5 support and includes the ability to preview what HTML5-based designs will look like across multiple devices.

The add-on pack includes code hinting support for HTML5 and CSS3, supports CSS3 media queries, includes several HTML5 starter layouts, updates the Dreamweaver’s WebKit engine with support for video and audio in preview mode, includes the ability to layout Web site designs for multiple screen sizes at the same time, and more.

The add-on will be good news for Web developers that need to move away from Flash-based Web site designs, or need to add HTML5 support to current Web sites. It also better positions the company to address concerns over whether or not it planned to offer full HTML5 support in its tools or focus on pushing Flash exclusively.

Interest in Adobe’s stance on Flash and HTML5 increased after the company found itself in a public feud with Apple over Flash support for the iPhone, iPod touch and iPad. Apple currently doesn’t support Adobe’s multimedia format on its portable devices, and won’t approve apps for the devices if they’re built with third-party tools that don’t natively support Apple APIs — including Flash CS5.

While Adobe has been promoting Flash as the best solution for online media delivery and Web-based apps, Apple has thrown its weight behind HTML5, CSS and the H.264 video format.

The Dreamweaver CS5 HTML5 Pack is an extension for the application instead of an update. It’s free and available for download at the Adobe Labs Web site.



Thanks Adobe, this may just be what I needed to convince me to shell out the money to upgrade. Very exciting news.


Too bad Adobe didn’t just do this from the start instead of trying to shove Flash garbage down everyone’s throats first.


Good move on Adobe’s part.

Too bad Adobe didn?t just do this from the start instead of trying to shove Flash garbage down everyone?s throats first.

I think you’re right, Adobe seems to have dragged their feet on supporting Flash, web standards, et al. while they have been putting a lot of work in the Flash platform.  I have little doubt that Adobe would have loved for the entire Web to be written in Flash.


Too bad Adobe didn?t just do this from the start instead of trying to shove Flash garbage down everyone?s throats first.

This is good news. I tend to agree; I’m far more in favor of Adobe developing for upcoming HTML 5 standards than giving you a way to tinker around with Flash in your print publishing software.


It will interesting, to say the least, to see whether Abode accepts the idea that it will have to build tools on the open standards as specified in Section 3.3.1 or whether it is trying its own version of the old Microsoft embrace and extend strategy in an effort to hinder the development of open standards for interactive content and redirect that to development with Adobe’s proprietary tools.

However, if Adobe genuinely intends to fully and sincerely support the open source, as specified in Section 3.3.1, that fully support the iPhone OS’s public APIs, then the dispute between Apple and Adobe could be moving toward resolution.  And the Web, users, and developers will all be the better for it.


Adobe will adopt HTML5 right up until the point that they dump it. It came to my attention (I wasn’t paying attention apparently!) that they have a new ally: Google. Instead of adopting the H.264 codec entirely, Adobe will start pushing Google’s just-announced, competitor : WebM, using the VP8 codec. The avantage: No royalty fee for programmers. For now.

As we’ve all seen, tech is transient.

Constable Odo

Smart move by Adobe.  If it can support HTML5, I don’t know why such a big stink was made over Apple not supporting Flash.  So what if their HTML5 product can’t do all the things that their Flash compiler can.  Some of those Flash developers tend to get too carried away with their Flash-heavy sites.  They need to tone some of that crap down.  I’m very happy that there is going to be an alternative to Flash only sites even if the transition starts slowly.


Now THIS makes sense - let’s get Flash back into the “vector graphic animations” category of content creation and let the people who create operating systems do the best job at THAT.

Flash is (currently) a sub-operating system running within another operating system and its critics are correct; it creates security holes and exploitation opportunities. 

HTML5 CSS3 and H.264 are the proper places to do much of what Adobe would purport Flash is the best solution. 

Friedrich Nietzsche said it [sic], “Change is pain”.  So let’s bite the bullet and get on with the technology solutions that make the most sense - even if it knocks Adobe back a notch - they’ll certainly survive and we’ll all prosper for doing the right thing.


Good business decision too. They’ll have tools available for their customers no matter which way the web tech pendulum swings.

Log in to comment (TMO, Twitter or Facebook) or Register for a TMO account