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.

Sign up for GitHub

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

Jump to bottom

Constants require an interface prototype object which callback interfaces don't have #281

Closed
tobie opened this issue Jan 24, 2017 · 0 comments
Closed

Constants require an interface prototype object which callback interfaces don't have #281

tobie opened this issue Jan 24, 2017 · 0 comments

Comments

@tobie
Copy link
Collaborator

tobie commented Jan 24, 2017

No description provided.

@tobie tobie changed the title Constants require a interface prototype object which callback interfaces don't have Constants require an interface prototype object which callback interfaces don't have Jan 24, 2017
tobie added a commit to tobie/webidl that referenced this issue Feb 2, 2017
@tobie
Don't require an interface prototype object for constants.
7dfd134 
Callback interfaces do not have an interface prototype object.
Their constants sit on the legacy callback interface object itself.

Closes whatwg#281.
@tobie tobie mentioned this issue Feb 2, 2017
Closed
tobie added a commit to tobie/webidl that referenced this issue Feb 14, 2017
@tobie
Don't require an interface prototype object for constants.
6df3be6 
Callback interfaces do not have an interface prototype object.
Their constants sit on the legacy callback interface object itself.

Closes whatwg#281.
tobie added a commit to tobie/webidl that referenced this issue Feb 20, 2017
@tobie
Don't require an interface prototype object for constants.
b5c51e9 
Callback interfaces do not have an interface prototype object.
Their constants sit on the legacy callback interface object itself.

Closes whatwg#281.
@tobie tobie mentioned this issue Feb 20, 2017
Merged
tobie added a commit to tobie/webidl that referenced this issue Feb 20, 2017
@tobie
Don't require an interface prototype object for constants.
4ecbd80 
Callback interfaces do not have an interface prototype object.
Their constants sit on the legacy callback interface object itself.

Closes whatwg#281.
tobie added a commit that referenced this issue Feb 20, 2017
@tobie
Revamp interface bindings (#313)
4a8f57e 
* Extract legacy callback interface objects
  out of interface objects. Closes #78.
* Clarify that legacy callback interfaces are function objects.
* Give them a length property. Closes #279. Closes #83.
* Require new for Named Constructors. Closes #275.
* Rely on ES abstract operations for defining
  named constructors, interface objects, and
  legacy callback interface objects.
* Disallow using [NoInterfaceObject] on
  callback interfaces with constants.
* Don't require an interface prototype object for constants.
  Callback interfaces do not have an interface prototype object.
  Their constants sit on the legacy callback interface object itself.
  Closes #281.

Closes #283.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tobie