Flag Direct Sockets API as pending #1553
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The API used to have a "pending" standing because its status was "Unofficial Draft Proposal". That seems good (and the proposal has a negative standard position from Mozilla). The status of the spec changed to "Draft Community Group Report" recently, which was enough to make our code switch the standing to "good". I missed that change when I reviewed the diff of web-specs and released a version of web-specs with that updated standing. This means Webref now tries to curate the IDL defined in the spec, and fails because the IDL references the `[IsolatedContext]` extended attribute that currently exists as a monkey patch in the Isolated Contexts spec. We may of course update Strudy to accept `[IsolatedContext]` but I'm thinking that the right standing for the spec remains "pending" for now. This update forces the standing accordingly.
dontcallmedom
approved these changes
Nov 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The API used to have a "pending" standing because its status was "Unofficial Draft Proposal". That seems good (and the proposal has a negative standard position from Mozilla). The status of the spec changed to "Draft Community Group Report" recently, which was enough to make our code switch the standing to "good".
I missed that change when I reviewed the diff of web-specs and released a version of web-specs with that updated standing. This means Webref now tries to curate the IDL defined in the spec, and fails because the IDL references the
[IsolatedContext]extended attribute that currently exists as a monkey patch in the Isolated Contexts spec.We may of course update Strudy to accept
[IsolatedContext]but I'm thinking that the right standing for the spec remains "pending" for now. This update forces the standing accordingly.