This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The Media Source Extensions spec is already assuming it can do this: interface MediaSource { ... enum State { "closed", "open", "ended" }; readonly attribute State readyState; ... }; The question then is whether you should be allowed to refer to MediaSource::State from some other interface.
What is the use case though? Enums can just as well be put in the global scope, they're not exposed anyway.
True that. And it looks like they have moved the enum out of the interface now.