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

MIDIInputMap - Conflict with Maplike? #118

Closed
ghost opened this issue Feb 25, 2015 · 3 comments
Closed

MIDIInputMap - Conflict with Maplike? #118

ghost opened this issue Feb 25, 2015 · 3 comments

Comments

@ghost
Copy link

ghost commented Feb 25, 2015

In the current Web MIDI spec the MIDIInputMap interface appears to conflict with the maplike Web IDL definitions that are used by Blink.

Blink's Web IDL file for MIDIInputMap looks like this:

[
    NoInterfaceObject,
    GarbageCollected,
] interface MIDIInputMap {
    readonly attribute unsigned long size;
    readonly maplike<DOMString, MIDIInput>;
};

According to the Web IDL specification the use of maplike is conflicting with the MIDIInputMap interface, for example the maplike values() function returns an iterator (not a function) and accepts no arguments (not a function).

This is true for the MIDIOutputMap interface as well.

Has the Web MIDI specification not been updated to take advantage of ES6 iterable types, or have the Web IDL files been defined incorrectly?

@toyoshim
Copy link
Contributor

Is this the same root with #115 ?

@cwilso
Copy link
Contributor

cwilso commented Feb 25, 2015

Yes. And last I checked, ReSpec doesn't support maplike yet, so we may have to just stop using respec.

@cwilso cwilso closed this as completed Feb 25, 2015
@ghost
Copy link
Author

ghost commented Feb 25, 2015

Sorry guys, I didn't know this was a duplicate.

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

No branches or pull requests

2 participants