Steps: Build latest fennec for ARM version 0.4 or download it from http://people.mozilla.org/~dougt/fennec-0.4/fennec-0.4.en-US.linux-arm.tar.gz Run fennec and open page www.fishki.net After first page paint (canvas update) try to pan content and drag/scroll it. EXPECTED OUTCOME: Canvas view always responsive and ready to pan. ACTUAL OUTCOME: Page loading (images, long content), and canvas view almost not responsive.

I was playing with latest fennec 21f625bd9726 with news.google.com... And after clicking on some random link I got next page: http://www.businessweek.com/careers/managementiq/archives/2008/10/damaging_capito.html After first visible update/paint I start to drag and scroll canvas content, but it was almost not possible or very very slow.... Probably this problem not reproducible on phone gprs connection, but it is very good visible on my home connection (~16Mb). Can we do anything with canvas event loop? make it somehow higher priority, or move it in separate thread?

this is substantially better now, but will leave open for additional work

Can we close this now? It's marked as blocking, but there's no description of additional work needed.

vote for not blocking1.0 - it's good enough to not block 1.0 I think we _should_ close this and open new bugs as needed

OK, talked with Stuart... we need to look at the knobs exposed through the GECKO_REFLOW environment variables and see how turning them affects interactivity with complicated pages. We want to err on the side of slower flow, since the devices are slower and used don't want to be blocked.

this is pretty good now, but will leave open for 1.1 for some additional work

tested www.lemonde.fr with b2 fennec and N900. We still have lot of short freezes on Fennec while loading page, Microb still works much more responsive and don't freeze at all on that page (even with flash content)

Closing all opened bug in a graveyard component