HTML and CSS Reference
■ the Bugmark test Suite (see figure 14-3 ) has been included with the code for this chapter. each test is
encapsulted, requiring construct, render, and destroy functions. the tests are sequenced, initiated with a number of
bugs to render, and timed for a given period. results are delivered to screen for ease of use.
run the tests on all the devices you can find to get a sense of performance across the board. there are some very
interesting results to note on smart televisions.
Disambiguation: the “bugs” referenced here are the little yellow and orange guys flying around the screen.
Figure 14-3. The Bugmark Test Suite
The Scooby-Doo game was designed for kids. Young audiences access the Web, through desktop computers,
much more than the mobile Web, on smartphone or tablets. There is a much higher-than-average use of older
browsers—meaning those that don't implement the canvas element.
Canvas should be the obvious choice for any HTML5 game rendering, but with Funfair Freak-Out , potentially up
to 20 percent of the audience wouldn't be reached. A difficult decision had to be made.
Benchmarking told us that DOM rendering would fulfill all our requirements within specification and reach
100 percent of our audience. As time goes on, and the old-browser percentage reduces, reasons for not using
Canvas are dissipating. DOM isn't going away and so will still work, but there isn't a whole lot of HTML5 about it.
Web Audio API and other HTML5 components were still used in the project, but when it came to rendering, we felt
it neater to have a single method.