Bug 112946

Summary: TestRunner::display driven requestAnimationFrame tests times out
Product: WebKit Reporter: Rafael Brandao <rafael.lobo>
Component: New BugsAssignee: Rafael Brandao <rafael.lobo>
Status: NEW    
Severity: Normal CC: benjamin, jamesr, jturcotte, kbalazs, kenneth, noam, sergio
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Rafael Brandao
Reported 2013-03-21 11:58:07 PDT
TestRunner::display driven requestAnimationFrame tests times out
Attachments
Patch (3.09 KB, patch)
2013-03-21 11:58 PDT, Rafael Brandao 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Rafael Brandao
Comment 1 2013-03-21 11:58:51 PDT
Created attachment 194312 [details] Patch
Rafael Brandao
Comment 2 2013-03-21 11:59:46 PDT
Comment on attachment 194312 [details] Patch This patch is not for review yet, just to show the issue.
Rafael Brandao
Comment 3 2013-03-21 12:07:05 PDT
On bug 112582, I've tried to create a display-driven test, given that TestRunner::display simulates a flush on the browser and triggers rAF calls (see https://bugs.webkit.org/show_bug.cgi?id=112582#c17). It seems to make sense, but this does not work for Chromium, Qt and Nix (will test other ports). The odd thing is that if I add to the end of the js file a setTimeout which calls notifyDone, then the whole test passes. I've tried to look for a while but didn't find anything useful so far, maybe it is a problem on how we manage the work queue. There was also some discussion on whether rAF should ever be display-driven anyway, so we could also move the discussion to here. I'm assuming here that display is correct.
Note You need to log in before you can comment on or make changes to this bug.