Comment #2 on issue 1704 by kpreid.switchb.org: es5 failures on firefox
aurora (22.0a2)
http://code.google.com/p/google-caja/issues/detail?id=1704
In order to fix the immediate problem, we just need to add a
CanvasLinearGradient to the WeakMap sanity check.
In order to fix the general problem, we need either:
1. a list of all the types of objects to test,
2. the type which Mozilla will end up fixing *last*,
3. some other way of detecting when Firefox has sorted out this problem, or
3. to always use the double weak map (which has a constant cost and good GC
properties as long as the browser WeakMap is not broken).
--
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/groups/opt_out.
