Closed GoogleCodeExporter closed 9 years ago
Ah, I think this is due do the js compressor, which seems to merge the
crypto.js file
with one of the hash files (like md5.js or sha1.js). So including crypto-md5.js
and
crypto-sha1.js does redefine the Crypto object.
For the sake of others reading this, the correct way do use both MD5 and SHA1
in the
same page is to include 3 separate files:
crypto/crypto.js
md5/md5.js
sha1/sha1.js
Then everything works fine.
So I guess it's not a bug, but what do you think? Worth mentioning in the docs
somewhere?
Original comment by bradcu...@gmail.com
on 9 Apr 2010 at 4:56
At minimum, worth mentioning in the docs.
Future versions will either prevent the crypto object from being overwritten,
or throw an error to at least alert the developer to what it happening.
Original comment by Jeff.Mott.OR
on 18 Jun 2010 at 5:49
awesome, thanks for the response
Original comment by bradcu...@gmail.com
on 20 Jun 2010 at 3:12
Fixed in revision 292.
Original comment by Jeff.Mott.OR
on 7 Mar 2011 at 3:58
Original issue reported on code.google.com by
bradcu...@gmail.com
on 9 Apr 2010 at 4:43