What’s a cookie? How do I protect myself on the web? And most importantly: What happens if a truck runs over my laptop?
For things you’ve always wanted to know about the web but were afraid to ask, read on.
OPEN BOOK
This illustrated book was designed for HTML5-compliant browsers and will not work with your current browser.
For the best viewing experience, please upgrade to the latest version of your browser or download a modern browser and try launching this site again.
What’s a cookie? How do I protect myself on the web? And most importantly: What happens if a truck runs over my laptop?
For things you’ve always wanted to know about the web but were afraid to ask, read on.
OPEN BOOK
How much does a plug-in interface with a browser? Curiously, hardly at all. The plug-in model is a lot like picture-in-a-picture on TV: the browser defines a distinct space on the web page for the plug-in, then steps aside. The plug-in is free to operate inside that space, independent of the browser.
This independence means that a particular plug-in can work across many different browsers. However, that ubiquity also makes plug-ins prime targets for browser security attacks. Your computer is even more vulnerable to security attacks if you’re running plug-ins that aren't up to date, because out-of-date plug-ins don’t contain the latest security fixes.
The plug-in model we use today is largely the one inherited from the web’s early days. But the web community is now looking at new
ways to modernize plug-ins — like clever ways to integrate plug-ins more seamlessly so that their content is searchable, linkable, and can interact with the rest of the web page. More importantly, some browser vendors and plug-in providers now collaborate to protect users from security risks. For example, the Google Chrome and Adobe Flash Player teams have worked together to integrate Flash Player into the browser. Chrome’s auto-update mechanism helps ensure that the Flash Player plug-in is never out-of-date and always receives the latest security fixes and patches.
You can pick up from where you left off the last time, or start at the beginning. Do you want to:
RESUMEBrian Rakowski, Ian Fette, Chris DiBona, Alex Russell, Erik Kay, Jim Roskind, Mike Belshe, Dimitri Glazkov, Henry Bridge, Gregor Hochmuth, Jeffrey Chang, Mark Larson, Aaron Boodman, Wieland Holfelder, Jochen Eisinger, Bernhard Bauer, Adam Barth, Cory Ferreria, Erik Arvidsson, John Abd-Malek, Carlos Pizano, Justin Schuh, Wan-Teh Chang, Vangelis Kokkevis, Mike Jazayeri, Brad Chen, Darin Fisher, Johanna Wittig, Maxim Lobanov, Marion Fabing Nicolas, Jana Vorechovska, Daniele De Santis, Laura van Nigtevegt, Wojtek Cyprys, Dudley Carr, Richard Rabbat, Ji Lee, Glen Murphy, Valdean Klump, Aaron Koblin, Paul Irish, John Fu, Chris Wright, Sarah Nahm, Christos Apartoglou, Meredith Papp, Eric Antonow, Eitan Bencuya, Jay Nancarrow, Ben Lee, Gina Weakley, Linus Upson, Sundar Pichai & The Google Chrome Team
Built in HTML5 
THING 1
or, 'You Say Tomato, I Say TCP/IP'
THING 2
or, why it's ok for a truck to crush your laptop
THING 3
or, 'Life, Liberty and the Pursuit of Appiness'
THING 4
or, this is not your mom's AJAX
THING 5
or, in the beginning there was no <video>
THING 6
or, browsing with more depth
THING 7
or, old vs. modern browsers
THING 8
or, pepperoni for your cheese pizza
THING 9
or, superpowers for your browser
THING 10
or, why it's ok for a truck to crush your laptop, part II
THING 12
or, giving you choices to protect your privacy in the browser
THING 13
or, if it quacks like a duck but isn't a duck
THING 14
or, beware the ne'er-do-wells!
THING 15
or, 'my name is URL'
THING 16
or, the phantom phone booth
THING 17
or, "Dr. Livingstone, I presume?"
THING 18
or, speeding up images, video, and JavaScript on the web
THING 19
or, standing on the shoulders of giants
THING 20
or, a day in the clouds