Leon

I feel like my recent colourisation of Javascript engines sort-of fulfills the intended purpose of the last checkbox.

I don't have any strong opinions about defining non-obsolescence. The heuristics we've been using up to now have been these: - The current stable version for auto-updating rapid-release browsers (Firefox...

There are two large (but not insurmountable) problems with testing modules: 1) Modules are async (same problem with testing Promise) 2) Modules require a `` tag - testing support for...

Summary of the extra tests: - Hoisted block functions can't clobber `let`/`const` bindings - Hoisted block functions can clobber simple parameter bindings. - Hoisted block functions can clobber complex parameter...

You could add support for [Elements](https://dom.spec.whatwg.org/#element-collections) which should be a subclass of Array, but that isn't finalised yet, I think.

Just a note: there is already a test on [this page](http://kangax.github.io/compat-table/strict-mode/) for legacy octals in strict mode.

The principle for adding tests that I've been using throughout these pages is "does the spec for this ES version introduce a meaningful change from the previous versions". This gets...

"the next few days"... :/ Anyway, the actual bones of subclassing now looks like this: - instantation of all exotic behaviour is done in the parent constructor instead of `@@create()`...

Update on this: it won't crash if the overlay is added after CodeMirror has finished the initial render of the passage, but it will crash if it's used before that...

EDIT: Hang on, coming up with another test case...