-
Notifications
You must be signed in to change notification settings - Fork 157
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
No mixin [NoInterfaceObject] usage #430
Comments
Here's a manually filtered list I build for #363 based on running awk on Gecko's src files:
|
Thanks, seems like we could just drop the keyword from those and be done with it. I guess part of the problem is some of those specifications not being maintained, but that can be fixed one way or another. |
Well, we'd want to make sure suddenly exposing these interfaces to the Web doesn't break stuff, no? |
Yeah, I suppose the ones with overly generic names should be prefixed, but seems safe otherwise. |
Prefixing is an observable change. No idea if it would have real impact, though. |
How is it observable? |
navigator.geolocation.getCurrentPosition(p => console.log(Object.prototype.toString.call(p)));
// [object Position] |
Sigh. Part of the reason we had [NoInterfaceObject] was the ability to ship objects and change the name later. I guess that's another reason we should really get rid of it (and decide on names we can live with upfront). |
WebGL seems fixed. I filed issues against two other specifications I identified from the list above. Anything else? |
Searching through Blink, |
Also https://w3c.github.io/webappsec-feature-policy/#featurepolicy ... a little hard to tell since Blink doesn't have interface mixin syntax yet, so lots of stuff is mixed together. |
Hiding interface objects is no longer a thing the web platform does. Helps with whatwg/webidl#430.
Fwiw, that's why I haven't looked at this in Gecko either. It'll be a lot simpler once we implement mixin syntax... |
Hiding interface objects is no longer a thing the web platform does. Helps with whatwg/webidl#430.
Hiding interface objects is no longer a thing the web platform does. Helps with whatwg/webidl#430.
Hiding interface objects is no longer a thing the web platform does. Helps with whatwg/webidl#430.
Per #423 (comment) this exists. I'd like to study such usage and see if we can get rid of it.
The text was updated successfully, but these errors were encountered: