This is about the new W3 WebcryptoAPI draft standard - http://www.w3.org/2012/webcrypto/WebCryptoAPI/
Here is a post by one of it's authors
https://plus.google.com/u/0/105761279104103278252/posts/CSwVZ1RUijo
It says its in part trying to change the "Javascript Cryptography Considered Hamrful" problem. However if you look at the "Javascript Cryptography Considered Hamrful" article - http://www.matasano.com/articles/javascript-cryptography/ - it seems as if most of the problems still remain unsolved. The only problem solved is that you won't have hand coded cryptographic functions in javascript - these will be provided by the browser. However, the remaining problems still remain.
Your thoughts?