<input type='passwordhash' hash='sha256' salt='26:$:9' editable='false'>
The actual password would have to be backed in RAM if the field is set to editable. But if it isn't, upon editing it would clear the current input.
Having hashes stored instead of actual passwords is of course not a total solution because someone savvy enough could use those same hashes to login to your services - but it definitely is better than plaintext - and will help stop novices from jacking your passwords. This of course requires both web dev and browser acceptance, I believe it's the future way to go
With the salt option, a website could use a different salt for changing your password or for doing certain 'secure' actions. This would prevent wholesale catastrophe when an account is hijacked, effectively a salt-based level system.
Thoughts?