With all due respect, nothing posted here was dangerous or pointless because nobody was saying that client side password hashing should be used instead of https. The question was whether or not client side hashing should be used in addition to https, salted hashed server storage, and 2FA. Is there any scenario where client side hashing would increase security? Any form of attack it might prevent? The answer is actually yes, if done correctly.
If your web session is ENCRYPTED and AUTHENTICATED using SSL, then you have to ask why you would want additional browser side encryption (SSL is, after all, a way of securing the data you send to the server).
To increase resistance to SSL failures and side channel attacks at the server. The first is unlikely, but not impossible. Sadly the second seems to be increasingly likely over time. (Owning your own hardware can mitigate it somewhat, but not completely.)
Again: client side hashing/encryption should never become a substitute for any of the other steps. If done correctly it may mitigate a SSL leak (though not a MITM) or a server side channel attack. No guarantees though.