Sergey Rubanov
Sergey Rubanov
It's because of Flattr and / or other 3rd-party scripts. @kangax could we remove some of them?
Exploit description https://nvd.nist.gov/vuln/detail/CVE-2016-7201 Actually it seems that the problem with memory corruption could be on our side. @jcscott2015 please more info if that's possible.
IMO we can fix problem on our side too if it's easy enough
Rhino's compatibility table http://mozilla.github.io/rhino/compat/engines.html
compat-table shows not only stable features. Actually all features from esnext tab are unstable. We should indicate if some ebvironments support those features (no matter under distinct flag or not)
I still don't agree with you. > An unstable feature means it is not complete yet and may change. All esnext features are unstable in that meaning. > An unstable...
> My patch keeps the note on how to enable them, just removes the "flagged" marking. That does make sense to me. Let's see what others think
Seems like we have consensus here. #1173 is merged
@kangax this needs Babylon parser support first and this work was started by @DrewML recently :) https://github.com/babel/babylon/pull/236
`npm run build` and `npm run build:compilers` both work on v0.10.48. Would be great if @webbedspace will chime in.