You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
To get a more complete list, the followin steps could (should?) be taken:
Try to get a definitive list of Objects with all their (class/instance/prototype) properties and compare that with what Rhino has at runtime. Not sure of such a list already exists, other than in the EcmaScript spec or maybe just the docs on MDN. Could try to scrape MDN or extract stuff from the EcmaScript spec
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
a = new java.util.HashMap() { b: 1 }
, alse see Next steps for Rhino after the v1.7.14 release #972 (reply in thread)To get a more complete list, the followin steps could (should?) be taken:
The text was updated successfully, but these errors were encountered: