When https://github.com/immersive-web/webxr/issues/347 is closed Chrome needs to implement the timestamp logic that was decided upon. Moste likely this will be identical to the timestamp logic for window.requestAnimationFrame().
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2a20abecf7b0957393948f74e1eee907b68547d6 commit 2a20abecf7b0957393948f74e1eee907b68547d6 Author: Brandon Jones <bajones@chromium.org> Date: Thu Jul 19 21:12:10 2018 Updated the timestamp XRSession frames provide The new timestamp is compatible with the one provided to window.requestAnimationFrame callbacks. Bug: 864756 Change-Id: Ia68762a150b9d2c4a4760564f8d48aac7c689e94 Reviewed-on: https://chromium-review.googlesource.com/1142227 Reviewed-by: Klaus Weidner <klausw@chromium.org> Reviewed-by: Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Brandon Jones <bajones@chromium.org> Cr-Commit-Position: refs/heads/master@{#576629} [add] https://crrev.com/2a20abecf7b0957393948f74e1eee907b68547d6/third_party/WebKit/LayoutTests/xr/xrSession_requestAnimationFrame_timestamp.html [modify] https://crrev.com/2a20abecf7b0957393948f74e1eee907b68547d6/third_party/blink/renderer/modules/xr/xr_frame_provider.cc [modify] https://crrev.com/2a20abecf7b0957393948f74e1eee907b68547d6/third_party/blink/renderer/modules/xr/xr_frame_provider.h [modify] https://crrev.com/2a20abecf7b0957393948f74e1eee907b68547d6/third_party/blink/renderer/modules/xr/xr_frame_request_callback_collection.cc [modify] https://crrev.com/2a20abecf7b0957393948f74e1eee907b68547d6/third_party/blink/renderer/modules/xr/xr_frame_request_callback_collection.h [modify] https://crrev.com/2a20abecf7b0957393948f74e1eee907b68547d6/third_party/blink/renderer/modules/xr/xr_session.cc [modify] https://crrev.com/2a20abecf7b0957393948f74e1eee907b68547d6/third_party/blink/renderer/modules/xr/xr_session.h
Issue 832201 has been merged into this issue.
Comment 1 by ddorwin@chromium.org
, Jul 17