15712 2012-01-25 18:34:07 +0000 CSSTransformValue should not use named constants 2012-01-31 21:00:24 +0000 1 1 1 Unclassified CSS Transforms unspecified All All RESOLVED WONTFIX P2 normal --- 1 ayg smfr cmarrin dino dschulze eoconnor smfr oldest_to_newest 63111 0 ayg 2012-01-25 18:34:07 +0000 CSSTransformValue's operationType is defined as an unsigned short. This is a bad pattern that the web platform is trying to move away from, because it requires authors to do things like if (list.operationType == CSSTransformValue.CSS_TRANSLATE3D) Instead, it should be a string, so that you can instead do if (list.operationType == "translate3d") This has the added benefit that alert(list.operationType) will output something sensible, like "rotateX" instead of "14". Likewise, looking at the variable in a debugger will display something sensible. Numbers are harder to use, and don't serve any good purpose. I'm assuming that CSSTransformValue isn't yet implemented by multiple UAs, only WebKit, so it can still be changed. Note that AFAICT, even WebKit only allows you to get one with the non-standard .getCSSPropertyValue() method. 63448 1 smfr 2012-01-31 21:00:24 +0000 We modeled this after CSSRule, which uses enums <http://dev.w3.org/csswg/cssom/#the-cssrule-interface>