Skip to content
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

What does [Exposed] mean on [LegacyNoInterfaceObject] interfaces? #919

Closed
saschanaz opened this issue Sep 17, 2020 · 4 comments · Fixed by #920
Closed

What does [Exposed] mean on [LegacyNoInterfaceObject] interfaces? #919

saschanaz opened this issue Sep 17, 2020 · 4 comments · Fixed by #920

Comments

@saschanaz
Copy link
Member

Currently the spec allows [Exposed] and [LegacyNoInterfaceObject] coexist with Example 74, while [Exposed] is optional in such case.

What does it mean to have both, though?

@annevk
Copy link
Member

annevk commented Sep 17, 2020

The way I see [Exposed] is as a list of globals/realm that can have instances of the object "present in them". And the other is really about whether the global object has a property pointing toward the constructor.

@saschanaz
Copy link
Member Author

Makes sense, but then does [LegacyNoInterfaceObject] alone implicitly mean [Exposed=Everywhere]?

@annevk
Copy link
Member

annevk commented Sep 17, 2020

I strongly suspect it appearing alone to be an error. I thought we required Exposed. If we don't, we should.

@saschanaz
Copy link
Member Author

We don't, #423 somehow allowed omitting it.

https://github.com/heycam/webidl/blob/6bccbcaf3a22c658e342fb032ebac7cc24c7836f/index.bs#L1019-L1021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants