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 BOOKBrowser extensions can also act on their own, outside of web pages. An email notifier extension can live on your browser toolbar, quietly check for new messages in your email account and let you know when one arrives. In this case, the extension is always working in the background no matter what web page you’re looking at — and you don’t have to log in to your email in a separate window to see if you have new messages.
When browser extensions were first introduced, developers often had to build them in unusual programming languages or in heavy-duty mainstream languages like C++. This took a lot of work, time and expertise. Adding more code to the browser also added to security concerns, as it gave attackers more chances to exploit the browser. Because the code was sometimes arcane, extensions were notorious for causing browser crashes, too.
Today, most browsers let developers write extensions in the basic, friendly programming languages of the web: HTML, JavaScript and CSS. Those are the same languages used to build most modern web apps and web pages, so today’s extensions are much closer cousins to the web apps and pages they work with. They’re faster and easier to build, safer, and get better and better right along with the web standards they’re built upon.
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