#430: WebXR Gamepads Module
Discussions
Discussed
Nov 1, 2019 (See Github)
bump to f2
Comment by @hober Dec 3, 2019 (See Github)
Marking this as pending external feedback
given the two issues @ylafon raised/linked above.
Discussed
Mar 1, 2020 (See Github)
Tess: Breakout in Cupertino looked at this. As output from that, Yves filed 2 issues on their spec, which are both still open. Marked ours as "pending external feedback" waiting for those to be closed. But I haven't looked at this one at all. (Not sure who else was in that breakout.) I should look at the explainer. Do we want to do anything in terms of the open issues?
Tess: Related to this spec monkeypatching the regular gamepad spec, which it shouldn't. Looks like not any movement.
David: links to https://github.com/w3ctag/design-principles/issues/99
Tess: Nell's latest comment was a question to the TAG about what to do here -- Yves answered the specific question, I think it's a satisfactory answer. Should we file an issue on design-principles to handle this case in general? Should we do more?
David: I'm not wild about the registry idea; I guess a registry is better than partials, though.
Tess: A registry results in a central list, partials doesn't get you that. From a platform maintenance POV that's what we want. There are other problems with registries, but it's an improvement.
David: There is a question of whether it's a registry or a spec edit.
Tess: Yves is providing a specific answer for this specific problem, either answer would be fine. Any sufficiently small and bespoke registry is indistinguishable from spec editing.
David: It's whether it does/should go through a different process.
Tess: I'd probably prefer the spec editing process myself, but either works.
Tess: We should probably give some indication that this came up today and we're waiting on those issues to be resolved. Left a comment.
Tess: let's pick a new milestone
Alice: 3 weeks
Comment by @hober Mar 16, 2020 (See Github)
Took another look at this in our APAC/USA breakout today. This is still pending resolution of immersive-web/webxr-gamepads-module#6 and immersive-web/webxr-gamepads-module#27
Discussed
Apr 1, 2020 (See Github)
(see minutes above)
Yves: I don't think it's a huge issue... The other issues about negative/positive seemed a bit more concerning. Issue #27 on their repo. They have to coordinate with the gamepad people. They marked this as pre CR so they must fix it before it before it goes to CR. Looks like they have agreed.
Sangwhan: some mixed opinions about the monkey patching.
Yves: I can live with it. We raised it. They've made an informed decision.
Sangwhan: they wanted to do it this way because it's unclear when the gamepad spec will go to CR. Technically, i think monkey patching is not great ergonomically.
Ken: things get out of sync.
Dan: but we are OK with it - I agree with Yves's comment that we have raised the issue. I think we should close, considering they are addressing both the issues that we've raised
Discussed
Apr 1, 2020 (See Github)
Tess: We raised a couple issues and set it as PEF, few weeks ago we checked, and a couple hours ago they are still open. What should we do? Leave open or something else?
Tess: The issues are around the monkeypatching design.
Tess: Yves and Dan are both on Breakout C; I'd like each of them to take a look to see if they have ideas for what to do next here
Discussed
Apr 1, 2020 (See Github)
Dan: Tess was happy to live with it thought it is a bit of a hack... but we have given our feedback
Ken: their issue #27 has "needs resolution" and Yves says we shouldn't close it...
[closed]
Comment by @torgo Apr 21, 2020 (See Github)
We have taken the decision today to close this issue. The only pending item we have is immersive-web/webxr-gamepads-module#27 which we will still keep track off through the external issue tracking mechanism.
OpenedOct 10, 2019
Hello TAG!
I'm requesting a TAG review of:
Further details: This is an extension of the WebXR API: https://immersive-web.github.io/webxr/
We recommend the explainer to be in Markdown. On top of the usual information expected in the explainer, it is strongly recommended to add:
We'd prefer the TAG provide feedback as (please select one):
Please preview the issue and check that the links work before submitting. In particular, if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document.
¹ For background, see our explanation of how to write a good explainer.