An easy workaround is to use a text document to copy and paste into last pass notes. I copied my site notes to a text file, added the carriage returns I wanted and pasted back to site notes. Very easy edit. Still looking forward to LP fixing this
If people could stop sharing copy & paste workaround, anyone has probably thought of it and tested it. We just want a fix from LP ! How can a simple but so annoying bug like that take more than 10 days to fix ???
They are aware and are working on it as also stated above, I guess your comment to my post was just as (if not more) useless as my unintentional repeat of the interim workaround.
Very rapidly losing patience on this now. It is a major user interface issue but is clearly simple to fix (it works fine on different types of entries - such as secure notes and credit cards - it is only Password entries which have the issue so it clearly isn't something fundamental). It seems that it occurred when Lastpass deployed the update which flags weak passwords etc. Those feature can wait. Roll it back and make the UI work again. Then deploy the new features once everything is TESTED properly. Plenty of people having the issue as per this thread, and others (e.g. https://community.logmein.com/t5/LastPass-Support-Discussions/Unable-to-use-quot-return-quot-key-whe...)
It also seems to be related to the issue with not being able to expand the edit window to full screen any more (which stopped working at exactly the same time - presumably with the same update?) - https://community.logmein.com/t5/LastPass-Support-Discussions/No-longer-able-to-make-Notes-field-lar...
Why is this taking so long to fix? I am a premium subscriber, but this is not premium service. Please fix asap now? This is getting beyond a joke.
I don't think anyone is fretting about the problem too much. My rub is that the communication is challenging. It seems like this community is not connected to the support organization. I wanted to make sure to report it and get a confirmation that the problem is acknowledged.
If I am the only one who reports it, they will ignore it. I am glad other people are also confirming this little bug is an issue. That's how RFE's and bug requests work. If only one in a million mention it, and nobody from product support acknowledges it, it never gets fixed. And the fact that LP pretty-much tripled the subscription charges in the past 2 years, I'd think they'd want to offer world-class quality and support.
Did you see that this problem is 3 years old? I saw that when I searched for it in this community.
No it just started about a week or so ago. I've been a last pass user for years and this has never been an issue for me before. I reported it immediately (you will notice I am one of the first people to comment on this old thread) and was assured that they were aware of the problem and working it. I have a case. I also posted here. That person whom reported the problem years ago might have been a glitch or bug back at that time.