Bug 138339

Summary: Re-evaluate if a repetitive timer should be throttled upon firing
Product: WebKit Reporter: Chris Dumez <cdumez>
Component: UI EventsAssignee: Chris Dumez <cdumez>
Status: RESOLVED FIXED    
Severity: Normal CC: barraclough, commit-queue, kling, koivisto
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 136197    
Bug Blocks: 138292    
Attachments:
Description Flags
Patch none

Chris Dumez
Reported 2014-11-03 17:33:46 PST
We should re-evaluate if a repetitive timer should be throttled upon firing in case the plugin observability state has changed: - It used to be visible but now isn't and thus the timer can be throttled - It used to play audio but now doesn't and thus the timer can be throttled We already stop throttling if the plugin becomes observable. However, we don't start throttling if the plugin becomes non-observable.
Attachments
Patch (2.39 KB, patch)
2014-11-03 17:52 PST, Chris Dumez 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Chris Dumez
Comment 1 2014-11-03 17:52:23 PST
Created attachment 240891 [details] Patch
WebKit Commit Bot
Comment 2 2014-11-05 10:43:14 PST
Comment on attachment 240891 [details] Patch Clearing flags on attachment: 240891 Committed r175627: <http://trac.webkit.org/changeset/175627>
WebKit Commit Bot
Comment 3 2014-11-05 10:43:17 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.