Repository navigation
Conversation
This conversion was done automatically and the output manually checked against the original ReSpec version.
Some editorial changes are necessary to comply with the different linting rules.
|
@annevk, since the rewrite is mostly mechanical what I'm looking for here is that I got all the metadata and build tooling set up correctly for a WHATWG spec. |
| understand the ways in which granting access to a device breaks traditional | ||
| isolation boundaries in the web security model. Security UI and documentation | ||
| should explain that granting a site access to a device could give the site full | ||
| control over the device and any data contained within. |
There was a problem hiding this comment.
I don't immediately see the Acknowledgments and IPR sections are specifications have. Again I recommend looking at whatwg/dom and whatwg/infra for copypasta.
There was a problem hiding this comment.
I've added an Acknowledgements section based on what I've seen in other specs and the IPR section seems to have magically appeared. Is there any tooling to keep this updated like how ReSpec could pull automatically from the Git commit history?
|
It seems this is missing many support files. I don't think you have run https://github.com/whatwg/spec-factory, is that right? Some of this is documented at https://github.com/whatwg/meta/blob/main/NEW-STANDARD.md but it could be more detailed. |
Thanks, I noticed spec-factory but misinterpreted it as part of the build and deploy pipeline rather than how the repositories themselves were created.
Thanks, I was looking for that checklist last week because I'd seen it before but forgot where. |
This branch has not been deployed
2 participants
This PR is an automated rewrite of the original specification from ReSpec to Bikeshed which has been manually checked against the original and then had the metadata updated to convert it from a W3C WICG draft report to a WHATWG Living Standard.