W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

[Bug 19936] consider allowing non-matching enums to be converted to a particular value

From: <bugzilla@jessica.w3.org>
Date: Tue, 13 Nov 2012 21:41:00 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-19936-2532-vMuYGU1jJu@http.www.w3.org/Bugs/Public/>

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
                 CC|                            |travil@microsoft.com

--- Comment #4 from Travis Leithead [MSFT] <travil@microsoft.com> ---
I think this is a good idea--I was personally always a little turned off by the
throw-on-not-matched behavior of enums (though I understand the rationale for

I'd propose a slight syntax change. Instead of:

enum CanvasContextName {
    "2d", "webgl", default = ""

the following seems more appropriate:
enum CanvasContextName {
    "2d", "webgl", "" = default

which would allow you to re-use enums for input elements:

enum InputTypeEnum {
    "text" = default,

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 13 November 2012 21:41:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:04:27 UTC