This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26452 - Introduce an explicit syntax for mixins
Summary: Introduce an explicit syntax for mixins
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-29 07:28 UTC by Ms2ger
Modified: 2017-10-11 21:16 UTC (History)
5 users (show)

See Also:

Attachments

Description Ms2ger 2014-07-29 07:28:18 UTC 
Rather than

[NoInterfaceObject] interface Foo {};

and somehow communicating that it's meant to be a mixin, we could use

mixin Foo {};

(or whatever) and only allow mixins on the RHS of |implements|.
Comment 1 Domenic Denicola 2014-08-01 22:09:06 UTC 
+1, this is a great idea. I constantly live in fear that someone will do `: Foo` instead of `implements Foo` with one of the "mixin" [NoInterfaceObject]s.
Comment 2 Boris Zbarsky 2016-10-15 01:38:09 UTC 
This needs to get done.  Everyone in the WebIDL discussions at the last TPAC agreed we need to do this, it'll make a sane fix for https://github.com/heycam/webidl/issues/164 possible, and is generally needed to make various parts of the spec less handwavy.
Comment 3 Tobie Langel 2017-10-11 21:16:29 UTC 
Fixed in https://github.com/heycam/webidl/pull/433/commits/8900c39