I myself noticed this problem a couple or three weeks or so ago, never before that.
To be clear, the problem is only in the Password edit dialog, and only on certain platforms (Chrome extension on Windows and MacOS; I haven't tested any other browsers or operating systems). It does NOT happen on the IOS (iPhone and iPad) LastPass app, or on the Mac Lastpass app.
It is apparent that the Password edit dialog window was changed to tie the Return key to the Save button action. It occurs everywhere in the Password edit dialog, not just the Notes field. Try typing Return in the folder dropdown, and the same thing happens (dialog closes and current state of the Password edits are saved).
I understand that this is frustrating, but this is an annoyance at best; it's not a show stopper. I rely heavily on LastPass and I can live with this for a while. I also understand that it takes time to push an update out; there's a development process, packaging, then QA and beta testing. Hopefully better testing than the prior release 🙂
There's also no point to yelling with all caps or red text at the support staff who read this forum. I'm sure they're passing the information back to development.
I believe we will be deploying an extension update soon that includes a fix for this issue. We will post another update once we have a firm release date.
Here are three easy workarounds while we're waiting for a new release to fix this problem, starting with the simplest:
1. Edit the Password note in the LastPass app on your iPhone, iPad, or use the MacOS Lastpass App (I assume it also works on Android phones and tablets, but I haven't tested that).
2. Open a new Secure Note, type a return, copy it to the clipboard, and go back to the Password note you want to edit. Instead of typing Return, type the Paste shortcut (CTRL/V or Command/V). This works because the bug only affects the Password dialog box, not the Secure Note dialog. No need to export the entire note text to another app.
3. Compose the the note text in a Secure Note (or an external text editor), then copy and paste it into the Password note field.
Personally, I have found this to be a minor annoyance. And I would much rather have the development team take the time to ensure that the next release fixes this problem but also is tested so that it doesn't introduce a new problem than rush to deploy a fix that isn't well tested.
I ended up using my phone to make the edits. Thanks for your other work-arounds. I hope that they truly are thorough and get things right. I also hope they fix the extension in Edge so that Start Up Boost can work.
This is simply unbelievable that a paid product left this error in production for a day - let alone months. If the development team can't get this right - what level of confidence should the community have that the same team can actually protect our most important information with the right level of care and diligence?
Stating the issue is "Solved" and when going to the "Solution" it says that you acknowledge the problem exists and a solutions is 'coming'-----does not mean it is solved. The advertised work-arounds, are annoying at best and a waste of time. Please get this fixed ASAP, as you are actively harming a lot of users.