Sending the plain text password to the server is the way to go
There is no advantage in doing that, and many disadvantages.
since you can't and should not trust the client to do any cryptographic work for you with it.
Hashing on the client is an additional level of security, not a replacement for existing levels, so no extra "trust" is required.
But what you SHOULD do for sure is use HTTPS...
then it doesn't matter that it's plain text, using HTTPS will be your encryption for sending it over the network.
HTTPS only protects you during transmission It does not protect you from server side attacks or from dishonest/incompetent employees.
Chrome has started flagging pages that have login forms submitting to HTTP to notify users the page is not secure. Good move.
Yes, that is a good move. The next step would be to warn users if their just typed password is being transmitted in plaintext. That would encourage best practices, and would have prevented the leak described in TFA.