Re: [fxtf-drafts] Update WebIDL definition(s) to use new mixin syntax

I think the question is not whether it should be a separate interface, but rather why it shouldn’t have an interface object. Note that having an interface object doesn’t automatically make the interface constructable: you have to explicitly declare `[Constructor]` to do that. See e.g. HTML element classes: they are not (ordinarily) constructable yet they do have an interface object. 

We usually only use `[NoInterfaceObject]` for really special cases where it is necessary (like web compatibility or security concerns). The fact that Firefox is fine without the extended attribute is a sign that it is unnecessary. 

-- 
GitHub Notification of comment by TimothyGu
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/233#issuecomment-354403595 using your GitHub account

Received on Friday, 29 December 2017 06:17:38 UTC