18:57:27 RRSAgent has joined #immersive-web 18:57:27 logging to https://www.w3.org/2020/05/26-immersive-web-irc 18:58:20 agenda+ administrivia#96 Virtual TPAC??? [AdaRoseCannon] 18:58:45 agenda+ webxr#1036 "Ensure an immersive device" cannot be run in parallel [Manishearth] 18:59:02 agenda+ webxr#1041 Reporting pose data depends on the state of the document? [Manishearth] 18:59:09 present+ 18:59:20 agenda+ webxr#1058 Various changes around null and emulated poses [Manishearth] 18:59:30 zakim, clear agenda 18:59:30 agenda cleared 18:59:33 agenda+ administrivia#96 Virtual TPAC??? [AdaRoseCannon] 18:59:36 agenda+ webxr#1036 "Ensure an immersive device" cannot be run in parallel [Manishearth] 19:00:03 agenda+ webxr#1041 Reporting pose data depends on the state of the document? [Manishearth] 19:00:03 cwervo has joined #immersive-web 19:00:09 agenda+ webxr#1058 Various changes around null and emulated poses [Manishearth] 19:00:13 zakim, list agenda 19:00:13 I see 4 items remaining on the agenda: 19:00:14 bajones has joined #Immersive-Web 19:00:15 1. administrivia#96 Virtual TPAC??? [from AdaRoseCannon via atsushi] 19:00:15 2. webxr#1036 "Ensure an immersive device" cannot be run in parallel [from Manishearth via atsushi] 19:00:15 3. webxr#1041 Reporting pose data depends on the state of the document? [from Manishearth via atsushi] 19:00:15 4. webxr#1058 Various changes around null and emulated poses [from Manishearth via atsushi] 19:00:25 +present 19:00:25 agenda: https://github.com/immersive-web/administrivia/blob/master/meetings/wg/2020-05-26-Immersive_Web_Working_Group_Teleconference-agenda.md 19:01:00 rrsagent, make log public 19:01:08 rrsagent, publish minutes v2 19:01:08 I have made the request to generate https://www.w3.org/2020/05/26-immersive-web-minutes.html atsushi 19:01:10 Leonard has joined #immersive-web 19:01:11 +present 19:01:30 date: 26 May, 2020 19:01:39 meeting: Immersive Web Working Group Teleconference - 2020-05-26 19:01:59 previous meeting: https://www.w3.org/2020/05/12-immersive-web-minutes.html 19:02:24 present+ 19:02:25 yonet: please present+ again; bajones, cwervo: use present+ instead of +present 19:02:45 present+ 19:02:50 rrsagent, publish minutes v2 19:02:50 I have made the request to generate https://www.w3.org/2020/05/26-immersive-web-minutes.html atsushi 19:03:02 cabanier has joined #immersive-web 19:03:03 present+ 19:03:08 present+ 19:03:23 RafaelCintron has joined #immersive-web 19:03:24 alcooper has joined #immersive-web 19:03:53 bialpio has joined #immersive-web 19:04:07 kip has joined #immersive-web 19:04:43 dino has joined #immersive-web 19:05:04 present+ 19:07:24 present+\ 19:07:25 present+ 19:07:38 avadacatavra has joined #immersive-web 19:07:38 scribenick: cabanier 19:07:43 alexturn has joined #immersive-web 19:08:04 topic: administrivia#96 Virtual TPAC 19:08:10 ada: there is no tpac 19:08:16 cwilso: w3c made tpac virtual 19:08:45 ada: we were thinking so we hold a weeklong of one hour meetings? 19:08:57 ... or just ignore it and just have our regular meeting 19:09:07 q+ 19:09:07 ... or have a video chat all day long? 19:09:16 ... does anyone have any suggestions? 19:09:22 q+ 19:09:46 ... please drop us an email and we'll try to work something out 19:09:49 ack L 19:09:56 ack Leonard 19:10:08 Leonard: I've been in several meeting. Let's restirct to 2-3 hours and no weekends 19:10:21 ... maybe tuesday-thursday 19:10:28 ... just give us enough notive 19:10:29 artem has joined #immersive-web 19:10:37 ... 4+ hours is too long 19:10:50 ack bajones 19:10:55 bajones: I agree with Leonard 19:11:00 q+ 19:11:18 ... more beneficial to break it into smaller meetings 19:11:24 ... we also have time zone issues 19:11:52 ... it also depends on the agenda items 19:11:53 My statement wasn't recorded correctly: It should be no meetings on weekends, but the meeting could run on multiple weeks. 19:11:56 q+ 19:12:34 ada: replicating the TPAC is a non-goal for me. Very stressful 19:12:41 ... so something less intense would be nice 19:12:56 ... but having shared meetings with other groups is nice 19:13:12 ... does anyone thing we should meet with other groups 19:13:14 ack avadacatavra 19:13:41 avadacatavra: I did TPAC virtually last year and it was painful because of time zone and family issues 19:14:10 ... it can be rough if it's one hour each day especially if it's the middle of the night 19:14:21 ... it's better if it's one full day 19:14:42 +1 for hubs! 19:14:45 ... also, mozilla hubs is great for this. I've used it before and it works really well 19:14:57 ... the social part is great 19:15:00 +1 and hearts for hubs 19:15:18 ada: if any group should use hubs, it's us! 19:15:35 avadacatavra: hubs is mozilla's social vr experience 19:15:43 ... work in vr but also in 2d 19:15:52 ... it has spatialized audio 19:16:02 ada: that's a great idea 19:16:09 ack Manishearth 19:16:28 Manishearth: if we want to do more than 2 hour of meetings, we should split it out 19:16:48 ... sometimes people want to step back and have a small meeting 19:17:00 dino: the css group had a virtual meeting 19:17:27 ... which worked out great. it went over several weeks 19:17:29 ack Leonard 19:18:03 Leonard: I agree with the timing of the meetings. ??? started meetings earlier to accomodate other time zone 19:18:08 q+ 19:18:20 ... if it's US and Europe, do it early in the day 19:18:39 ... it's good to have social and hallway meeeting 19:18:54 ack ada 19:19:26 ada: one thing that would work well. Over a week we'd have meetings over 3 days 19:19:45 +1 to Ada's suggestion 19:19:46 ... and we'd group people in meetings that they care about in the right time zones 19:19:49 +1 19:19:49 +1 19:20:08 ... I'll make a strawman proposal and then we'll see it from there 19:20:33 ... I'll do that this coming week but please email suggestions 19:20:46 zakim, take up agendum 2 19:20:46 agendum 2. "webxr#1036 "Ensure an immersive device" cannot be run in parallel" taken up [from Manishearth via atsushi] 19:21:07 Manishearth: this is a tricky issue because we've shipped a broken API 19:21:12 rrsagent, publish minutes v2 19:21:12 I have made the request to generate https://www.w3.org/2020/05/26-immersive-web-minutes.html atsushi 19:21:18 ... right now we support device selection 19:21:35 ...but we're relying on a synchronous mechanism 19:22:02 ... this is bad because the main thread is blocked 19:22:10 ... there are a couple of paths forward 19:22:28 ... the xrcompatible flag is there but not used by any UA 19:22:57 ... ??? but this will break existing content 19:23:07 https://github.com/immersive-web/webxr/issues/1036#issuecomment-629598102 19:23:16 ... the other option is to leave it as is 19:23:53 (see agenda description for all the options) 19:24:08 ... I'm leaning towards option 4 but I want to consider option 2 19:24:18 ... because I don't like the patching of this in the webxr spec 19:24:27 q+ 19:24:36 ack RafaelCintron 19:25:08 RafaelCintron: there are cl in the works to use the xrcompatible flag for use in hybrid devices 19:25:25 ... right now it completely doesn't work on their hardware 19:25:43 ... so the more we can solve this without breaking content, I'll prefer 19:26:00 ... I agree that all options are less than ideal 19:26:16 q+ 19:26:25 Manishearth: the tag and people from mozilla are opposed to slow synchronous 19:26:44 ... with the change devices that works should keep working 19:26:58 ack bajones 19:27:00 RafaelCintron: maybe we should require the xrcompatible flag. 19:27:06 Manishearth: that is my suggestion 19:27:23 bajones: I don't like that since we're not CR, we can break things 19:27:42 ... we should have recognition that this was something we preferred 19:27:43 q+ to mention that we should also consult with the WebGL group for their feedback. 19:27:56 ... this is already in place for webgl and canvas 2d 19:27:57 q+ 19:28:34 ... when you call getcontext you could force a context loss 19:28:49 ... but that is not a good option. it harms usability of the API 19:29:02 ... so what we picked avoided the worst path 19:29:16 ... the other thing was that we made the page xrcompatible 19:29:32 ... so that every context on that page would be xr compatible 19:29:42 ... we don't want slow and synchronous 19:30:02 q+ 19:30:04 ... we're backed into a corner because of the existing webgl behavior 19:30:21 ack kip 19:30:21 kip, you wanted to mention that we should also consult with the WebGL group for their feedback. 19:30:27 kip: given that we have some options, I got some feedback from the webgl group 19:30:31 q+ 19:30:35 ack Manishearth 19:30:37 ... we should fix it from the beginning 19:30:57 Manishearth: I don't agree that we should make breaking changes since we're not in CR 19:31:05 present+ 19:31:12 ... I don't like slow and synchround 19:31:37 ... but if we already have run device selection, we can give you the right devices right away 19:32:10 ... so the only time to get the context loss event is if you already run issessionsupported 19:32:23 ... if you haven't run issessionsupported 19:32:43 q? 19:32:48 RafaelCintron: there was an option where the webxr runtime gives you a context 19:32:49 sorry I fell off the internet 19:32:59 q+ 19:33:06 ... in that case, we'd have to care about context loss 19:33:14 q- 19:33:17 cwilso: could you chair? 19:33:32 q+ 19:33:36 ack raf 19:33:38 q- 19:33:48 ack ba 19:34:34 bajones: I wanted to point out that the context loss option is a terrible option for users 19:34:53 ... since they never expect this to option. some frameworks might handle it 19:35:35 ... in webgpu, the equivalent hook is asynchronous. so moving forward this problem will go away 19:36:14 ... it's not great to be synchronous, it's a result of legacy APIs 19:36:34 zakim, take up agendum 3 19:36:34 agendum 3. "webxr#1041 Reporting pose data depends on the state of the document?" taken up [from Manishearth via atsushi] 19:36:51 Manishearth: I will focus on this one since it's security related 19:37:02 cwilso has changed the topic to: https://github.com/immersive-web/administrivia/blob/master/meetings/wg/2020-05-26-Immersive_Web_Working_Group_Teleconference-agenda.md 19:37:09 ... we have a check in the spec about the hidden state of the document 19:37:26 ... so we don't return poses if the user is not interacting with the page 19:37:42 ... this might have unintended UX experiences 19:37:58 q+ to talk about XR topmost vs. 2D focus 19:38:00 ... also we should never throw during unexpected things 19:38:14 ... so we should return a null pose instead 19:38:20 q? 19:38:26 ack alexturn 19:38:26 alexturn, you wanted to talk about XR topmost vs. 2D focus 19:38:54 alexturn: we hit this on wmr and we ended a spit option on focus 19:39:19 ... there's the one traditional focus such as keyboard input 19:39:33 ... the way we handle xr stuff, it's more xr topmost 19:39:50 ... the thing that is on top of an xr scene gets the input 19:40:14 ... I don't have we can put this in spec text 19:40:40 ... if the user agent has logically switch away, everything should be going away 19:40:51 q+ 19:40:58 ... definitely exceptions shouldn't happen if the user switches away 19:40:59 ack bajones 19:41:09 q+ 19:41:24 bajones: yes, throwing exceptions is a bad thing. a pose of null is much better 19:41:37 ... I 19:41:59 q+ 19:42:09 ... I don't remember exactly where the original security spect text came from since John Pallet is no longer on the team 19:42:24 q+ 19:42:31 ... personally, clicking on devtools while in vr stops the scene which is a bit annoying 19:42:35 q+ 19:42:39 ack avadacatavra 19:43:09 avadacatavra: what I'm hearing, that the usability here is problematic 19:43:36 ... I'm unsure that the security angle is handled by null poses so we should go that route 19:43:49 bajones: can you expand that? 19:44:08 q+ to talk about how we already have XRVisibilityState to represent this discussion in a more nuanced way 19:44:16 avadacatavra: what we don't want that if you're not in focus, that the non-focused page gets input 19:44:35 ... what we're having, is if you're going away, you freeze 19:44:53 ... we shouldn't be errorring on that. We want null poses 19:45:06 q? 19:45:23 Manishearth: should we always have no poses when the document is hidden? 19:45:31 avadacatavra: I have to think about it 19:45:56 Manishearth: there seems consensus that there is no exception thrown 19:46:36 mounir: usually devices don't expose changes when the document is not visible 19:46:58 ... originally I was surprised about the focus usage in webxr 19:47:16 ... most pages still work while not in focus 19:47:29 a+ 19:47:31 q+ 19:47:37 ... the related API show if the page is visible 19:48:00 ... so maybe delaying until the page is visible again is an option 19:48:21 alexturn: I wanted to note that the spec is using document visibility 19:48:44 ... since we have the xr visibility state which was intended to work around this 19:48:45 q? 19:48:49 ack M 19:48:51 ack Manish 19:48:54 ack alexturn 19:48:54 alexturn, you wanted to talk about how we already have XRVisibilityState to represent this discussion in a more nuanced way 19:49:01 ... when you switch to a different tab 19:49:24 ... the middle state of visible blurred is to keep rendering but not get focus 19:49:40 q? 19:49:40 ... so maybe this is legacy content in the spec that needs to be updated 19:49:50 ack avadacatavra 19:50:29 avadacatavra: we're using visible blurred for simple yes/no but not for keyboard input 19:51:10 ... I'd say that in my opinion, there's no reason to throw a security error unless we can find the original issue that John Pallet was trying to fix 19:51:14 zakim, take up agendum 4 19:51:14 agendum 4. "webxr#1058 Various changes around null and emulated poses" taken up [from Manishearth via atsushi] 19:51:29 rrsagent, publish minutes v2 19:51:29 I have made the request to generate https://www.w3.org/2020/05/26-immersive-web-minutes.html atsushi 19:51:37 Manishearth: this handles a bunch of things around null poses 19:51:59 ... right now, poses are never null except if there have never been any poses during a session 19:52:17 s/present+\// 19:52:19 ... it makes sense for getviewerpose 19:52:33 present+ ada, alexturn, avadacatavra, bajones, dino, RafaelCintron 19:52:50 ... but this makes getpose return null 19:52:54 q+ to ask if input sources would just deenumerate 19:53:21 ack alexturn 19:53:21 alexturn, you wanted to ask if input sources would just deenumerate 19:53:24 ... it also fixes the 674 change, to get a reference space until it is trackable 19:53:27 q+ 19:53:27 q+ 19:53:48 alexturn: for something like a controller, it might go out of tracking fov 19:54:03 ... so is this for example when hands go out of space? 19:54:25 ... my model is during those times the hands are no longer enumerated 19:54:36 Manishearth: for input that works ok 19:54:40 ack bialpio 19:54:45 ... but not for anchors and fingers 19:55:11 q+ 19:55:25 bialpio: we should allow that null poses can be returned 19:55:29 ack alexturn 19:55:30 q? 19:55:42 ack bajones 19:55:42 ... since it fixes a number of issues 19:55:45 q+ alexturn 19:55:50 q+ alexturn 19:56:09 bajones: +1 to those. If the controller goes away for a long time, it should go away 19:56:23 q+ 19:56:40 ... ideally controller should never return null but it's not a restriction we can put on the space level 19:57:12 ... for anchor it makes sense to have pose values if it's far away 19:57:22 ack alexturn 19:57:49 alexturn: I agree with all this. Anywhere we remove edge cases we can more consistencies 19:58:15 ack Manishearth 19:58:19 ... if we carve it out and remove it from input source space, ??? 19:58:53 Manishearth: specifically for hand input, if it disappeard and comes back, the order in the array might have changed 19:59:04 ... this could lead to content missing things up 19:59:15 q+ 19:59:31 ack alexturn 19:59:34 ... for controllers we don't have this issue because even if they're out of fov, they are still in communication 19:59:53 q+ To mention that things like vive tracker's should probably not de-enumerate 20:00:03 alexturn: pages might get confused if your hands input goes away and comes back 20:00:21 ack kip 20:00:21 kip, you wanted to mention that things like vive tracker's should probably not de-enumerate 20:00:37 kip: vive trackers. you might have a bunch of them 20:00:53 ... if they disappeared and reappeared, the mapping would be lost each time 20:01:04 Manishearth: true. that's an issue 20:01:08 q+ 20:01:20 ack bialpio 20:01:34 q+ 20:01:48 ack avadacatavra 20:01:50 bialpio: a quick notice, we are giving sites raw camera access 20:02:09 avadacatavra: we are also experimenting with immersive navigation on hubs 20:02:48 ... and we're experimenting with immersive trusted UI 20:04:23 rrsagent, publish minutes v2 20:04:23 I have made the request to generate https://www.w3.org/2020/05/26-immersive-web-minutes.html atsushi 20:22:27 s/(see agenda)/... (see agenda)/ 20:23:00 s/... I$// 20:23:02 rrsagent, publish minutes v2 20:23:02 I have made the request to generate https://www.w3.org/2020/05/26-immersive-web-minutes.html atsushi 20:24:05 s|s/(see agenda)/... (see agenda)/|| 20:24:12 s/(see agenda /... (see agenda / 20:24:14 rrsagent, publish minutes v2 20:24:14 I have made the request to generate https://www.w3.org/2020/05/26-immersive-web-minutes.html atsushi 20:43:31 About hubs may I share this little demo : https://twitter.com/RzrFreeFr/status/1264481035896721409