Open tmedwards opened 4 years ago
How well does the Twine 2.x application's Test and Play options handle ES6 code?
The question is essentially moot for non-browser-shell Twine 2 releases as they all open in users' browsers, which puts the onus on the browser.
For the browser-shell releases, it depends on whether we're talking pre- or post- Twine 2 v2.3.
Make sense?
It's time to change SugarCube's baseline browser support.
Consider changing the baseline browser target to: