21424 2013-03-28 16:39:15 +0000 Futures: rename `catch` 2013-03-28 16:55:02 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC All RESOLVED WONTFIX P2 normal --- 1 mathias annevk d erik.arvidsson mathias mike www-dom public-webapps-bugzilla oldest_to_newest 85099 0 mathias 2013-03-28 16:39:15 +0000 `catch` used to be a reserved word in ES3: http://mothereff.in/js-properties#catch It would be better to use a different name that doesn’t cause syntax errors in older browsers, so that feature detection for Futures can be done without `try`/`catch`. 85101 1 d 2013-03-28 16:40:50 +0000 This shouldn't matter. `catch` is not what you feature-detect on; `then` is. 85102 2 erik.arvidsson 2013-03-28 16:49:24 +0000 All browsers supports ES5. I would mark this as WONT FIX 85103 3 annevk 2013-03-28 16:52:21 +0000 arv has spoken per expectations. Less work for me. Sorry Mathias! 85104 4 mathias 2013-03-28 16:53:30 +0000 (In reply to comment #1) > This shouldn't matter. `catch` is not what you feature-detect on; `then` is. (In reply to comment #1) > This shouldn't matter. `catch` is not what you feature-detect on; `then` is. Even then, any code that uses `catch` would throw a syntax error in ES3 environments. As per ES3: if (featureDetect) { this.catch; } // SyntaxError So, even if you don’t use `catch` in the feature detection snippet, it will still fail: if (featureDetect) { this.catch; } // SyntaxError As long as `catch` is used it means all code relying on Futures should be wrapped in a `try`/`catch` block to avoid throwing in ES3 environments. 85105 5 erik.arvidsson 2013-03-28 16:55:02 +0000 If you care about ES3 (and you shouldn't) you can always use member lookup: if (this['catch']) ...