Summary: | Take into consideration canvas drawing for throttling DOM timers | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Chris Dumez <cdumez> | ||||
Component: | Canvas | Assignee: | Chris Dumez <cdumez> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, barraclough, commit-queue, esprehn+autocc, gyuyoung.kim, jimoase, kling, koivisto | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Bug Depends on: | 139812 | ||||||
Bug Blocks: | 138292 | ||||||
Attachments: |
|
Description
Chris Dumez
2014-12-01 11:32:26 PST
Created attachment 242329 [details]
Patch
Comment on attachment 242329 [details]
Patch
r=me
Comment on attachment 242329 [details] Patch Clearing flags on attachment: 242329 Committed r176609: <http://trac.webkit.org/changeset/176609> All reviewed patches have been landed. Closing bug. What was the reason to have this fixed in a new bug, not in bug 139054 where the problem was reported? It is usually best to associate fixes with original reports. *** Bug 139054 has been marked as a duplicate of this bug. *** (In reply to comment #5) > What was the reason to have this fixed in a new bug, not in bug 139054 where > the problem was reported? It is usually best to associate fixes with > original reports. Sorry, I was only aware of the radar. Otherwise I wouldn't have bothered to create a new report. |