At 4:24 there's the worst bit: a big rendering chug while scrolling up, taking a long time to draw the mysymbian banner. In that time, the whole top half of the screen is blank for a quarter of a second. It's like watching Netscape Navigator 4 all over again :-)

In fact it has the delay twice there. It really looks like it happens when there are certain object types being rendered.

See what I mean about it only happening when zoomed in? And I notice, when scrolling up (to the start of the page); it doesn't happen scrolling down.

At 4:18-4:20 when you zoom out, there's a long delay in filling in the top and sides - more white gap.

When zoomed out, it's pretty consistently good. At 4:12, there's a white strip at the top of the browser - another rendering delay, perhaps. (It'd be less visible if it was black).

(I see lots of brief stalls in the kinetic scrolling, but that could easily be Youtube not the device).

Big rendering chug at 5:33. Ok, that's a task switch, we may expect more chugging then. (Though a really polished implementation would hide such things).

Indeed. To me it reminds me of browsers from an era gone by (waves to my old laptop). But it's usable, and no doubt will improve. It's a very superficial issue.

As someone who has worked on game engines, video playback devices and GUI toolkits, I tend to notice these little things and think "if only I it wasn't just me..."

I'm fascinated that you didn't see them in your own video. It really reminds me of my colleague who can't tell the difference between 30fps games and 60fps games - whereas I can tell immediately and they feel totally different to look at. No wonder people argue about these things if they're invisible - and therefore not an issue - to half the people