-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge 'end the session' with 'shut down the session', clarify, add onend event #710
Conversation
r? @toji |
@@ -443,8 +443,12 @@ When an {{XRSession}} is shut down the following steps are run: | |||
1. Set |session|'s [=ended=] value to <code>true</code>. | |||
1. If the [=active immersive session=] is equal to |session|, set the [=active immersive session=] to <code>null</code>. | |||
1. Remove |session| from the [=list of inline sessions=]. < 8000 /td> | |||
1. [=Reject=] any outstanding promises returned by |session| with an {{InvalidStateError}}. | |||
1. If no other features of the user agent are actively using them, perform the necessary platform-specific steps to shut down the device's tracking and rendering capabilities. | |||
1. [=Reject=] any outstanding promises returned by |session| with an {{InvalidStateError}}, except for any promises returned by {{XRSession/end()}}. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooh, hey! Good catch. 😅
index.bs
Outdated
1. [=Reject=] any outstanding promises returned by |session| with an {{InvalidStateError}}, except for any promises returned by {{XRSession/end()}}. | ||
1. If no other features of the user agent are actively using them, perform the necessary platform-specific steps to shut down the device's tracking and rendering capabilities. This MUST include: | ||
- Releasing [=exclusive access=] to the [=/XR device=]. | ||
- Deallocating any framebuffers attached by the |session| to the [=/XR device=]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Attached" doesn't seem like the right word here? Also it may not always be framebuffers specifically, so maybe something more like this (keeping in line with your recent swap chain PR)?
Deallocating any graphics resources acquired by the |session| for presentation to the [=/XR device=].
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense. Getting on a flight soon, will push this fix later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Safe travels!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
👏 |
Potential fix for #467
Not quite sure of this, also not sure of what precisely we should list in the platform specific steps.