delicious

WebDriver takes a different approach to solve the same problem as Selenium. Rather than being a JavaScript application running within the browser, it uses whichever mechanism is most appropriate to control the browser. For Firefox, this means that WebDriver is implemented as an extension. For IE, WebDriver makes use of IE's Automation controls. By changing the mechanism used to control the browser, we can circumvent the restrictions placed on the browser by the JavaScript security model. In those cases where automation through the browser isn't enough, WebDriver can make use of facilities offered by the Operating System. For example, on Windows we simulate typing at the OS level, which means we are more closely modeling how the user interacts with the browser, and that we can type into "file" input elements.

Using Image.onload/onerror + CSS tricks.

I wonder how the BBC's Dirac is coming too.

More fun canvas games!

Alex talks about the autoupdate issue. I personally lean towards autoupdate myself. I would love to take it further and have the browser as a microkernel with many updates.

"Clear scientific evidence shows that a stretching habit isn’t good for warmup, injury prevention, preventing or treating muscle soreness, enhancing athletic performance, or even for flexibility"

It's alive!

"Where NoScript went "evil" and drew this storm of criticism was with a recent update where NoScript would effectively modify Adblock Plus"