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 19:08:14 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-19936-2532-WwCGa9csfy@http.www.w3.org/Bugs/Public/>

Tab Atkins Jr. <jackalmage@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |jackalmage@gmail.com

--- Comment #3 from Tab Atkins Jr. <jackalmage@gmail.com> ---
(In reply to comment #2)
> It seems very awkward to me to express the default as part of the enum type.
> How common is this pattern? What's the value of using an enum rather than a
> DOMString here?

It's common in a lot of enumerated attributes in the DOM, such as <input type>.

The benefit of using an enum over a DOMString+explanatory text is the same
benefit of using an enum at all - it's simpler to read and write, and ensures
that we'll get consistent behavior.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 13 November 2012 19:08:17 UTC

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