Has testing before release been cut back deliberately?

Three times this year I have been adversely affected by 1P releasing buggy software - in ascending order of annoyance and concern:

• The first was different sort orders in browsers vs the desktop version (now fixed in the latest version I believe). In fairness, it is possible that this had been there for years without me realising it  and (eventually) raising it with support. it didn't affect data so was just an annoyance.
• The second was the frustration of safari constantly offering to save logins that 1P had just filled - I wasn't the only one affected by this - I am not sure if this one is fixed as I disabled some things as a (support suggested) workaround and haven't re-enabled them again yet.
• Todays Bug (Notes being truncated ) forced a passcode reset with a bank and cost another half an hour once I found the problem (I thought it was me and a specific note which I re-arranged and re-typed) before I thought to  check the community rather than the main support site. The bug is a 'Known Issue' according to the 1P reply posted 25 days ago!

The truncated notes bug hid information from me - it bcame visible when I clicked on the edit button (to put the new passcode in) but vanished once again when saved. Why is a bug of this severity (hiding info from customers) still not fixed? Why isn't there an alert?

I'm worried. Can 1P still be trusted?

Software quality seems to be in decline.

Do the new(ish) owners not care about testing prior to release?

Are they starving the testing team of resources?

Do they not realise that their entire business depends on customers believing that 1P can be trusted with their data - having a bug that hides data from customers, and which isn't mentioned in the main support database when customers look for it does not inspire me with confidence.