Closed Bug 1850110 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 41634 - Implement XR Session Section in chrome://webxr-internals

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox119 fixed)

Status:
RESOLVED FIXED
Milestone:
119 Branch
Tracking Flags:
Tracking Status
firefox119 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 41634 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/41634
Details from upstream follow.

Mahmoud Ahmed <mahmoudaahmedd@gmail.com> wrote:

Implement XR Session Section in chrome://webxr-internals

Summary:
This commit introduces the implementation of XR Session section
within the WebXR Internals debugging page.

  • XRSession Info: This section provides a display of information
    regarding the XR session. It includes details such as start time and
    session end time, along with trace id, mode, usage preferences,
    data format preferences and a list of required/optional features.

Bug: 1458662
Change-Id: I9ae09f37185999ac8cbf2f5150fbf99a12755f86
Reviewed-on: https://chromium-review.googlesource.com/4793733
WPT-Export-Revision: 41639ea66bb7e84499044586b2d26a3daf811257

The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Test result changes from PR not available.
Test result changes from PR not available.
Test result changes from PR not available.
Test result changes from PR not available.
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/073579fc2cd2 [wpt PR 41634] - Implement XR Session Section in chrome://webxr-internals, a=testonly

https://hg.mozilla.org/mozilla-central/rev/073579fc2cd2

Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox119: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
You need to log in before you can comment on or make changes to this bug.