Status: Started
Owner: [email protected]
Labels: Type-Defect Priority-Medium Component-Other
New issue 1932 by [email protected]: SES calls "new WeakMap(true)" which
is incorrect ES6 and no longer works on Canary
http://code.google.com/p/google-caja/issues/detail?id=1932
If "new WeakMap" is called with an argument, ES6 demands that the argument
be iterable. Chrome Canary now enforces that. However, SES's
ejectorsGuardsTrademarks.js calls "new WeakMap(true)" in two places, in
accordance with an early and long dead proposal for WeakMaps (also
implemented at one time by our shim) that the argument be an optional flag
that, if set to true, would be a hint that the weak association should be
optimized to use key lifetime rather than map lifetime.
The attached screenshot shows what currently happens loading the SES
initialization test on Chrome Canary.
Attachments:
ses-bug-weakmap.png 195 KB
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
