I'm saying disruption happens both ways: The innovators disrupt the laggards, but the innovators build up cruft and legacy over time and the laggards can side-step them and jump through revolutions.

We tend to get caught up in our own disruptions.

Do you mean "awkward to scroll" from a performance perspective or from a not-being-able-to-see-the-scrollbar perspective?

Sorry, performance perspective. It happens in incognito as well (no extensions).

Not sure why no one else is commenting about it though..

My pleasure, glad you enjoyed it :)

I acknowledge WebKit's monopoly on the mobile landscape today, I make no claim whether it's a good thing or a bad thing, that argument would distract from the reality that if you want to make a mobile web app work well, you need to build it on webkit and debug it on webkit

... and test it cross-browser. WebKit has a majority on mobile (around 75%) but not a monopoly. (Source: http://gs.statcounter.com/#mobile_browser-ww-monthly-201103-... )

But if you do your part to break it in other browsers you can help make your job easier and make it easier to innovate in the future.

Thanks for the comment. Was there anything specific you could point me to that you felt was above your head? I'd love to do a follow-up with more introductory material.

When you go to "About Google Chrome", do you see something close to "Version 20.0.1114.0 canary"?

I wasn't using Canary, I had Version 18..., thanks!

Thanks for letting me know, I didn't realize I broke that. I just pushed up a fix

Dunno if you've had that fix go live yet, but it's still unusable. The actual little scroll tracker (what's the name for that thing?) isn't discernible from the background. When you scroll up and down, the bar turns white and the cursor is white. I'd send a ss, but I don't see anyone else complaining so it's probably a me problem. Might be because I'm on Linux.

So the reason is because I have a black background color on body. When I said it's fixed, I just realized it's only fixed on Chrome Canary. It looks different on Chrome 18, and it looks different than that in Safari. Welcome to the Web. I'll try to fix it again after work.

Well, that's what you get when you hamstring yourself to developing in a daily build of your browser.

Don't get me wrong, I do the same thing, but you have to admit there is a certain dry humor in the fact that you recommended as a best practice to develop exclusively in a cutting edge build of a standards-based browser, only to find that your website is broken in every browser except your development one.

The choir hears you. Spent an hour today on some ie7 fix.

Chromium is the open source project that powers Chrome, the browser. Chrome Canary is upstream of Chromium, which is an upstream of Chrome.

Not quite true -- Chrome Canary is just a daily build from the Chromium repository.

You actually bring up a good point, the webkit inspector right now is tied to the webkit project, and the barrier to contribution is prohibitively high. I've suggested to Paul Irish separating the two projects and making them more independent, though I'm not sure what the feasibility of that is.

I can either try to submit a patch and likely fail, or blog about it. Last time I complained to Google about Chrome, they filed 33 bugs and fixed many of them. The point here is to be an agent of change, not an agent of patches :)

Ah damn! I had both those on my outline but forgot to write about them :( I'll update the post. Thanks :D