172942 2017-06-05 16:25:56 -0700 Update JSC's features.json 2017-06-06 09:42:20 -0700 1 1 1 Unclassified WebKit JavaScriptCore WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=172958 P2 Normal --- 1 saam saam benjamin ddkilzer fpizlo ggaren gskachkov jfbastien jond keith_miller mark.lam msaboff simon.fraser ticaiolima ysuzuki oldest_to_newest 1315815 0 saam 2017-06-05 16:25:56 -0700 ... 1315817 1 saam 2017-06-05 16:32:48 -0700 landed in: https://trac.webkit.org/changeset/217805/webkit 1315818 2 saam 2017-06-05 16:32:59 -0700 Rubber stamped by Mark Lam in person. 1315827 3 saam 2017-06-05 17:19:08 -0700 *** Bug 172865 has been marked as a duplicate of this bug. *** 1315880 4 ddkilzer 2017-06-05 20:55:13 -0700 The <https://webkit.org/status/> page may have broken after this change. Tried to fix it with: <https://trac.webkit.org/r217816> However, that didn't seem to change anything. 1315887 5 ddkilzer 2017-06-05 21:27:56 -0700 So I think the problem is that "ESNext" was used as a specification in a feature, but it wasn't listed in the "specification" section at the top of features.json. Should we change "ESNext" to "ES7", or add an entry for "ESNext"? { "name": "ES7", "url": "https://github.com/tc39/ecma262", "keywords": ["es7", "ecmascript"] }, { "name": "ESNext", "url": "https://tc39.github.io/ecma262/", "keywords": ["esnext", "ecmascript"] }, 1315893 6 saam 2017-06-05 21:51:43 -0700 (In reply to David Kilzer (:ddkilzer) from comment #5) > So I think the problem is that "ESNext" was used as a specification in a > feature, but it wasn't listed in the "specification" section at the top of > features.json. > > Should we change "ESNext" to "ES7", or add an entry for "ESNext"? > > { > "name": "ES7", > "url": "https://github.com/tc39/ecma262", > "keywords": ["es7", "ecmascript"] > }, > { > "name": "ESNext", > "url": "https://tc39.github.io/ecma262/", > "keywords": ["esnext", "ecmascript"] > }, I'll update with a new ESNext section. 1315894 7 saam 2017-06-05 21:51:53 -0700 (In reply to Saam Barati from comment #6) > (In reply to David Kilzer (:ddkilzer) from comment #5) > > So I think the problem is that "ESNext" was used as a specification in a > > feature, but it wasn't listed in the "specification" section at the top of > > features.json. > > > > Should we change "ESNext" to "ES7", or add an entry for "ESNext"? > > > > { > > "name": "ES7", > > "url": "https://github.com/tc39/ecma262", > > "keywords": ["es7", "ecmascript"] > > }, > > { > > "name": "ESNext", > > "url": "https://tc39.github.io/ecma262/", > > "keywords": ["esnext", "ecmascript"] > > }, > > I'll update with a new ESNext section. About to land now. 1315895 8 saam 2017-06-05 21:54:07 -0700 landed follow up ESNext section in: https://trac.webkit.org/changeset/217819/webkit Thanks for looking into this Dave. 1315896 9 saam 2017-06-05 21:54:49 -0700 https://webkit.org/status/ appears to work. 1315900 10 simon.fraser 2017-06-05 22:01:40 -0700 I filed bug 172958 to do more json validation.