-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
add WebUSB WebIDL #1712
add WebUSB WebIDL #1712
Conversation
Thanks for this! We in general only add stage 3 and beyond proposals to this repository. I can't seem to find documentation, but do you know at what stage in the standards process this proposal is at? |
I don't know where we can find the stage of the proposal... |
@alexcrichton I don't know what stage it is, but it is marked as Experimental on MDN, and only Chrome and Opera have support for it right now. In addition, MDN says that it's currently at Draft status, so it's definitely not stable. And the status section says this:
|
I wonder if maybe we should have support for unstable APIs, perhaps behind an And we would reserve the right to break anything behind |
Ok so it sounds like we shouldn't add this as-is because it's not an official spec yet, but I like the idea of having experimental specs here that we can break at any time. Prior art for that I'm aware of isn't to use Cargo features but rather That way it's a bit more experimental in that it forces consumers to always compile with the right flags. How's that sound to enable this? |
That sounds reasonable to me. It means that libraries will have a harder time relying upon unstable features, so they will be mostly used by applications, which is how it should be. |
@Pauan @alexcrichton thanks for comments. |
This hasn't seen movement in quite some time now so I'm going to close this, feel free to resubmit it though! |
FWIW I've opened #1950 to track longer-term about how we plan to support unstable WebIDL files. |
issue #1694