W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2012

[Bug 19101] New: consider allowing nested enum definitions

From: <bugzilla@jessica.w3.org>
Date: Fri, 28 Sep 2012 01:35:46 +0000
To: public-script-coord@w3.org
Message-ID: <bug-19101-3890@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19101

           Summary: consider allowing nested enum definitions
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebIDL
        AssignedTo: cam@mcc.id.au
        ReportedBy: cam@mcc.id.au
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-script-coord@w3.org


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.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 28 September 2012 01:35:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:07 UTC