This is a little silly IMHO, but not entirely unprecedented. Sadly, there seems to be more and more of a move towards building software to "protect the users from themselves".
It's the user's responsibility to make sure that they trust the folks who use their box, plain and simple. If you [the software developer] really, really, _really_ want to shield fools from themselves, then build in "keychain" functionality but just disable it by default. Why deprive sane users of a feature just because some users can't figure out how to use it in a safe, effective manner?
Chrome's stance is like the Linux kernel developers deciding to strip out swap support because some folks could use a laptop with an unencrypted swap partition.