GitLab

Having a RequestAnimationFrame API on CommandBuffer makes no sense - the
context itself has nothing to do with scheduling and may not even be
swapping onscreen.  The spinning cube app was using this API as a way to
get delayed tasks without depending on base - basically
posttask-via-mojo-message. This adds basic delayed task support to the
public RunLoop and uses that instead. This only supports posting tasks
from the thread that owns the runloop. We can expand as needed. The mojo
RunLoop attempts to interleave delayed tasks with handle handlers, like
base's MessageLoop.

Review URL: https://codereview.chromium.org/384513003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@285560 0039d316-1c4b-4281-b951-d872f2087c98