Comment #37 on issue 18537 by [email protected]: Scrolling is horrible due to an issue with background and color properties http://code.google.com/p/chromium/issues/detail?id=18537
We could make a modified page cycler that scrolls around in the browser after loading the page. Once the scrolling is complete on a given page, it moves on to the other pages. Another idea: use browser automation to simulate scrolling around in the browser. If a reduction+page cycler can isolate the performance hit we see, it would be better to go the page cycler route. It is both easier to add and modify existing page cyclers using the page_cycler_tests code rather than writing a new test routine that hooks into the browser automation. I've also found that running tests via JS is less fragile than using the automation since a reference build is usually involved in the tests (and the reference build automation code might be out-of-sync with ToT). If this is important to capture, please file a bug and mark me as owner. I'll look into it further and discuss scheduling with Mark. Thanks. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
