HTML and CSS Reference
This may seem obvious at this point, but the working groups creating these specifications are always open to public
comment and feedback throughout their development cycles. Don't feel that if you have a great idea or want to
see something added, changed, or removed from a specification that you won't have a voice. In fact, everyone
does; that is the beauty of the open Web! Submit your comments to the W3C, WHATWG, IAB, MMA, or whoever
makes the most sense based on your input. Although you may not get a response right away, I promise people are
listening. I'm one of them!
It's now time to end this discussion on where HTML5 is headed next and how the advertising industry is using it to
make your ad experiences more powerful and engaging than ever before. Some amazing things are coming to the
Web, and the truth is that this chapter is just scratching the surface. As more browsers, devices, working groups, and
technologies emerge and work together, you'll see a whole new landscape of bleeding-edge features. Keep in mind
that the more newer HTML5/CSS3 features you use, the more potential for those features to break with browser
updates. This is particularly the case with using prefixed drafts and beta only features. This typically means more
differences between browser implementations and ones that are more likely to change between their actual releases.
Lastly, it's pretty difficult to manage each and every API because there are just so many of them being developed
( http://dret.typepad.com/dretblog/html5-api-overview.html ). If you want to keep up with the most bleeding-
edge features, I strongly suggest reading the browser manufacturers' blogs, developer advocate articles, and the W3C's
and WHATWG's evolving specs. As you start to head into your final chapter, you'll be taking a holistic look at the entire
web advertising landscape and how HTML5 is impacting it all on every screen going forward.