-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Implement support for [LegacyWindowAlias]
and [NoInterfaceObject]
#191
Conversation
[LegacyWindowAlias]
[LegacyWindowAlias]
and [NoInterfaceObject]
[LegacyWindowAlias]
and [NoInterfaceObject]
[LegacyWindowAlias]
and [NoInterfaceObject]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems to make sense to implement [Exposed]
in this PR too, as it seems odd that the globalName
is only used for [LegacyWindowAlias]
. But up to you.
Co-Authored-By: Timothy Gu <[email protected]>
|
@@ -1420,7 +1463,7 @@ class Interface { | |||
const { idl, name } = this; | |||
|
|||
this.str += ` | |||
exports.install = function install(globalObject) { | |||
exports.install = (globalObject, globalName) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After re‑reading the spec for [Global]
and [Exposed]
, I realised that this needs globalNames
instead of globalName
.
I’m fixing that in #190.
This reverts the breaking changes introduced in #191, since it was accidentally released as a minor version in v15.2.0, while keeping the functionality.
This reverts the breaking changes introduced in #191, since it was accidentally released as a minor version in v15.2.0, while keeping the functionality.
Fixes #187
review?(@TimothyGu)