That was advice Adobe had no choice but to take, and in April 2011 Dreamweaver CS5.5 appeared, with its focus switched to HTML5 – and almost no mention of Flash. The blog post in which Jobs signed Flash’s death warrant concluded: “Perhaps Adobe should focus more on creating great HTML5 tools for the future, and less on criticizing Apple for leaving the past behind.” Like the W3C before it, Adobe was powerless to control the evolution of the web, and Flash went the way of XHTML. To deliver rich web content, and stream video to iOS devices, suddenly you had to embrace HTML5. Robbed of universal delivery on these next-generation devices, Flash in the browser was doomed to decline rapidly. Steve Jobs turned the web upside down by announcing, the day before the launch of Adobe’s Creative Suite 5, that Apple wouldn’t be supporting Flash on the iPhone or the iPad. I’ve covered the denouement of this tale extensively. Read our first-look review of Dreamweaver CC Also, since Flash was universally supported by desktop browsers, and could do everything HTML5 was promising to deliver – and plenty more besides – the need to switch to the less powerful, less universal HTML5 was debatable at best. As Adobe focused on this strategy, Dreamweaver looked increasingly like a tool merely for wrapping SWF-based Flash applications in HTML. Web designers, as a general rule, work to the lowest common denominator, which meant waiting until all non-HTML5 browsers had been flushed from the system – a very distant prospect.Īnother factor was that Adobe already had its own, extremely successful, web-application technology in Flash, and was determined to exploit the edge this granted it and its users.

The web is universal or it’s nothing, and there’s no point creating all-singing, all-dancing pages that most of your audience can’t view. To be fair, there were good practical reasons.

This ought to have promised exciting new features for the world’s most popular web-authoring tool, but Dreamweaver continued to act as if HTML5 didn’t exist. In 2009, the W3C accepted defeat, dumped its own XHTML working group, and embraced WHATWG’s initiative, handing the future of the web to the browser developers and their evolving HTML5.

Convert html to html5 dreamweaver