mirror of
https://github.com/rails/execjs
synced 2023-03-27 23:21:20 -04:00
Note ES5 limitations
This commit is contained in:
parent
3d605e9e38
commit
1816df22d1
1 changed files with 7 additions and 0 deletions
|
@ -57,6 +57,13 @@ consistent interface.
|
||||||
For similar reasons as modules, not all runtimes guarantee a full JavaScript
|
For similar reasons as modules, not all runtimes guarantee a full JavaScript
|
||||||
event loop. So `setTimeout`, `setInterval` and other timers are not defined.
|
event loop. So `setTimeout`, `setInterval` and other timers are not defined.
|
||||||
|
|
||||||
|
**Why can't I use ES5 features?**
|
||||||
|
|
||||||
|
Some runtimes like Node will implement many of the latest ES5 features. However
|
||||||
|
older stock runtimes like JSC on OSX and JScript on Windows may not. You should
|
||||||
|
only count on ES3 features being available. Prefer feature checking these APIs
|
||||||
|
rather than hard coding support for specific runtimes.
|
||||||
|
|
||||||
**Can I ExecJS be used to sandbox scripts?**
|
**Can I ExecJS be used to sandbox scripts?**
|
||||||
|
|
||||||
No, ExecJS shouldn't be used for any security related sandboxing. Since runtimes
|
No, ExecJS shouldn't be used for any security related sandboxing. Since runtimes
|
||||||
|
|
Loading…
Add table
Reference in a new issue