Commit 8e7e870d authored by Fernando Serboncini's avatar Fernando Serboncini Committed by Commit Bot

Don't use legacy time base for RAF callback

Legacy timer was never implemented on Worker.RAF, so we always return
the same value for both. Since they are identical, we might as well not
use "legacy".

Bug: 995235
Change-Id: I370171b6b2a082bbc850cd35956244b191611f0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796083
Commit-Queue: Fernando Serboncini <fserb@chromium.org>
Auto-Submit: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: default avatarMatt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#695649}
parent 18da217b
...@@ -566,7 +566,7 @@ int WorkerGlobalScope::requestAnimationFrame(V8FrameRequestCallback* callback, ...@@ -566,7 +566,7 @@ int WorkerGlobalScope::requestAnimationFrame(V8FrameRequestCallback* callback,
auto* frame_callback = auto* frame_callback =
MakeGarbageCollected<FrameRequestCallbackCollection::V8FrameCallback>( MakeGarbageCollected<FrameRequestCallbackCollection::V8FrameCallback>(
callback); callback);
frame_callback->SetUseLegacyTimeBase(true); frame_callback->SetUseLegacyTimeBase(false);
int ret = animation_frame_provider_->RegisterCallback(frame_callback); int ret = animation_frame_provider_->RegisterCallback(frame_callback);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment