2 ms·
It's just because NYT is positioning the chart stupidly (but probably most-reliably, knowing browsers...). It's absolute-positioned, and they're updating its '
by Groxx 16y ago
It's just because NYT is positioning the chart stupidly (but probably most-reliably, knowing browsers...).
It's absolute-positioned, and they're updating its 'top' when you scroll. WebKit has a fast enough JS engine that this sort of thing is seamless, but not every browser does / not on every computer.
edit: tried Firefox (4 beta), it's a handful of pixels off the top, and bobs. You'd think people would know about position: fixed by now.
- kmfrk 16y agoI see - I incorrectly inferred from the parent that the browser used was Chrome.