W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > December 2017

[mediacapture-main] Why is ConstrainablePattern using [NoInterfaceObject]?

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Mon, 18 Dec 2017 11:20:06 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issues.opened-282844791-1513596005-sysbot+gh@w3.org>
tobie has just created a new issue for https://github.com/w3c/mediacapture-main:

== Why is ConstrainablePattern using [NoInterfaceObject]? ==
`ConstrainablePattern` uses the [NoInterfaceObject] extended attribute, yet it's not a mixin, nor does it seem to need to do so for legacy compat reasons, which is now the [legit reason](https://heycam.github.io/webidl/#NoInterfaceObject) to use this extended attribute.

I suggest replacing the `ConstrainablePattern` interface's `[NoInterfaceObject]` extended attribute with the `[Exposed]` extended attribute, specifying the globals on which it should be exposed.



Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/501 using your GitHub account
Received on Monday, 18 December 2017 11:20:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:33 UTC