- From: Silvan Mosberger via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Jun 2022 21:37:47 +0000
- To: public-webauthn@w3.org
I'm a bit disappointed by W3C regarding this. - I saw something in the specification that I didn't understand how to implement in a library, so I opened [an issue](https://github.com/w3c/webauthn/issues/1699) asking for clarification. - A small [PR](https://github.com/w3c/webauthn/pull/1704) with a supposed fix was opened, however I [clearly stated](https://github.com/w3c/webauthn/pull/1704#issuecomment-1050043574) that it still didn't make any sense to me, but the PR was merged without addressing my points and the issue was deemed resolved. - I was told that I can propose another PR, which I did here. While the changes themselves aren't that important, I finally [understood](https://github.com/w3c/webauthn/pull/1718#issuecomment-1128023604) the real problem with the specification and made some clear suggestions for how it could be improved. - However again, it seems like the WG doesn't deem my concerns here valid and closes the PR, considering the issue resolved. At this point the specification is still as unclear as it was from the beginning, and I'm glad for @Firstyear backing me up here. So what should I do here? Leave it be and hope that everybody in the future figures out what the specification means themselves? Or should I try to open another PR, hoping that my concerns are taken seriously then? -- GitHub Notification of comment by infinisil Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1718#issuecomment-1154464470 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 June 2022 21:37:48 UTC