Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identify all non-EcmaScript behavior and extentions to disable/remove/make optional in v2.0.0 #1056

Open
14 tasks
p-bakker opened this issue Oct 14, 2021 · 1 comment
Labels

Comments

@p-bakker
Copy link
Collaborator

p-bakker commented Oct 14, 2021

In v2.0.0 we want to, by default, run Rhino with Context.VERSION.ECMASCRIPT (see #1055), which should give the user a clean, EcmaScript compliant JavaScript engine, with, by default, no (api) extensions

In order to achieve that goal, all non-standard behavior and API extensions need to be identified

To aid in this, one of the goals for v1.7.15 is to be able to run the latest version of the Test262 suite, so we can get good feedback on how standard-compliant Rhino is. Note that standard-compliant doesn't necessarily mean feature completeness.

Test262 however doesn't not report on non-compliant API extensions, so those need to be identified through other means.

See the Next steps for Rhino after the v1.7.14 release discussion for already identified EcmaScript incompatibilities in Rhino

(incomplete) list of incompatibilites

To get a more complete list, the followin steps could (should?) be taken:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant