I am deeply concerned that this request has not been given the priority it deserves. It represents a significant security risk that cannot be overlooked. As other posters have mentioned, there are password managers that have successfully implemented this feature, so there is no reason why it cannot be done in this case.
The fact that the request has been dismissed as “working as originally requested” is even more concerning, as it suggests that the internal R&D team has not fully appreciated the seriousness of the security implications of not implementing measures to hide and conceal these notes fields when the “require master password” option has been selected. This is far from “working as intended”. It is outright irresponsible and careless.
Rather than deflecting attention from the issue by talking about other features, it is important that the team demonstrate a real commitment to addressing security issues in the product. This means bumping up the priority of implementing this relatively straightforward feature, and showing users that their security concerns are being taken seriously.
Any attempt to rationalize or justify a decision not to pursue this feature is simply an indication of how little the team cares about addressing significant security issues. I urge the team to take this matter seriously and do everything possible to prioritize fixing this issue. It is essential to recognize that avoidant and dismissive responses, coupled with a lack of a clear timeline for implementation, will only serve to undermine user confidence in the product. The “kicking the can down the road” mentality is a poor strategy when it comes to addressing security concerns, and failure to do so may result in the loss of user trust and ultimately lead to people seeking out more secure alternatives.
In closing, It is essential that the team takes this issue seriously and demonstrates a real commitment to improving the security of the product.