- From: <bugzilla@jessica.w3.org>
- Date: Fri, 09 Dec 2011 19:15:51 +0000
- To: public-script-coord@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11451
Tab Atkins Jr. <jackalmage@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jackalmage@gmail.com
--- Comment #15 from Tab Atkins Jr. <jackalmage@gmail.com> 2011-12-09 19:15:51 UTC ---
(In reply to comment #14)
> I suppose that if you throw in the case of unrecognized values, then that's one
> way to feature-detect that you're running in a UA that doesn't support some new
> value of the enum.
>
> On the other hand, won't you be able to inspect the enum's values
> programmatically to ensure the string you want will be supported? In other
> words, given:
>
> enum A { "x", "y" };
>
> Is "A" exposed to JavaScript along with its values?
Some recent APIs that take dictionaries define the dict as an interface that
you can poke at to find support. It would be nice to have the same with enums.
--
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, 9 December 2011 19:15:53 UTC