-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow partial enums #184
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I'm seeing some more needs:
|
Even though it's more coordination work, I still think encouraging everyone to maintain centralized lists for these is good, per the rationale in w3ctag/design-principles#99. |
Agree with @annevk. More coordination seems preferable as it provides more checks and balances. |
This one is fairly simple to handle given that both specifications are part of the same WG and worked on by the same people.
The Permissions API already has a list of all permissions. Clipboard should just adds itself in there. |
Filed immersive-web/webxr-ar-module#32 and w3c/clipboard-apis#101 to fix them. |
Here's an example where we ran into this issue and added a comment, not great: |
@henbos Were there any blockers that prevents the WebXR way? (It added the extension to the original enum definition with a prose, which explains that its behavior is defined in another spec.) |
I was looking for whether we permit partial enums like we do extended interfaces, and found this bug:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27048
This doesn't seem to have concluded, but I couldn't find a similar bug in this repo.
FWIW, I think having partial enums is no more dangerous than partial dictionaries or partial interfaces; all of them can lead to name collisions if not well maintained. So I'm (so far) in favor of adding them.
The text was updated successfully, but these errors were encountered: