Immersive Web Working Group Teleconference - 2019-12-03

Important! We are really close to CR release. At the bottom of this email
are issues marked *help wanted*. The issues in the *pre-CR* milestone are
blockers for Candidate Recommendation. Tackling these issues would be a
great help!!

Also if you can, please read through the issues linked below before the
call, there needs to be discussion about them in the call so time will be
precious sorry that this email is so short notice.

Thanks, Ada & Chris
Call Agenda

This agenda can be viewed and updated on Github

If you would like to add an item to the agenda or volunteer to scribe
please open a pull request against this agenda.

   - webxr-gamepads-module#23 Should hand-based input sources have a
   <> requested
   by Manishearth

to be discussed alongside

   - webxr-input-profiles#105 Should we have a generic profile for hands?
   <> requested
   by Manishearth

to see what people think about a generic hands profile

   - webxr#900 Use permissions API for XR feature requests
   <> requested by

to ask people to look at it

   - webxr#929 Split input sources into primary/auxiliary
   <> - klausw

This introduces new definitions for primary/auxiliary XR input sources, and
"transient action" for transient input device to support a transient input
device that isn't a primary input source.

Immersive Web Working Group Teleconference - 2019-12-03
San Francisco (U.S.A. - California) Tuesday, December 3, 12:00 PM PST
Boston (U.S.A. - Massachusetts) Tuesday, December 3, 3:00 PM EST
London (United Kingdom - England) Tuesday, December 3, 8:00 PM GMT
Paris (France) Tuesday, December 3, 9:00 PM GMT+1
Tokyo (Japan) Wednesday, December 4, 5:00 AM GMT+9
Corresponding UTC (GMT) Tuesday, December 3, 8:00 PM UTC Logistics

Chair: Ada Rose Cannon


IRC: #immersive-web Instructions

Call Details can be found on the Internal Mailing List

If you are unable to login to view the call details please ask on the IRC
before the call.

For assistance go to and on the left
navigation bar, click "Support".
Help Wanted

Here are some issues which are good issues to get involved in, if you have
taken responsibility for one leave a comment in the issue:

   - webxr#225 Behavior of window.requestAnimationFrame and
   window.requestIdleCallback when presenting
   - webvr-polyfill-dpdb#34 Create a helper script/web page for generating
   values for a new device
   - webxr#603 What happens if a canvas with an xrCompatible context is
   attached to the DOM? <>
   - webxr#736 Should calling XRSession.requestAnimationFrame in a
   Window.animationFrameCallback be banned?
   - webxr#776 Remove unnecessary or redundant information from "Security,
   Privacy, and Comfort Considerations"
   - webxr#777 Requirements for native viewport size?
   - webxr-input-profiles#69 Resizing the window changes the model viewer's
   aspect ratio
   - webxr-gamepads-module#16 Add link to the registry
   - webxr#854 Result of calling checkFramebufferStatus on an opaque
   framebuffer <>
   - webxr#856 Do opaque framebuffers have a reference to their XR session?
   - webxr#860 What is a "valid feature descriptor"
   - webxr#877 Note somewhere that you should be always be queueing up the
   next rAF within rAF <>
   - webxr#880 Corrections and clarifications for description/steps for
   updateRenderState() <>
   - webxr#891 Clarify semantics of preserveDrawingBuffer
   - webxr-input-profiles#109 Oculus Touch S / Oculus Quest profiles
   - webxr#923 cancelAnimationFrame: clarify behavior when called from a
   frame callback <>

Received on Monday, 2 December 2019 22:46:53 UTC