- From: <bugzilla@jessica.w3.org>
- Date: Fri, 09 Dec 2011 18:59:24 +0000
- To: public-script-coord@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11451
--- Comment #14 from Travis Leithead [MSFT] <travil@microsoft.com> 2011-12-09 18:59:23 UTC ---
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?
--
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 18:59:26 UTC