Description: Menus opened in cascade close as soon as an option is selected. Steps to Reproduce: In Writer | Select Edit → Track changes → unselect Record. Actual Results: All menus opened in cascade close instantaneously. Such behavior illustrates a power of decision belonging to the application instead of the user. Expected Results: Not to close the menu which still has the pointer upon of it. | Under a currently displayed menu, a user may have several options to select/unselect in a row, e.g by going on with option Accept all. As a consequence of the current behaviour, the user has to reopen in a row those same menus as many times as there are options to be selected/unselected. A natural user/interface relation would exist only once that decision belongs to the natural application user, which is indeed the user not the application itself. The implementation in this regards would be to close the displayed menu as soon as the pointer is out of the menu’s frame, then without even the need for clicking somewhere out of the involved frame. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.1.5.2; Build ID: 10(Build:2); CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI: en-US; Calc: threaded Tested on Gnome 40.0 on Wayland.
For Tracking Change manage you can use the Track Changes toolbar with all commands I think your enhancement is not valid. Users expects main menu will hide after user select any item -1 from me Let's ask UX-team also
Do you know any application that keeps the menu open until... maybe you click escape? Point is that menus behave like this and we must not change the usual behavior.
Yet they are people to defend the position that users are expecting free software to be bad developed and kept as such and feel the need to demonstrate it as well. Won't you ever learn that once one from inside or outside your community has its mentality nothing can any more surprise. Today i must have been lucky enough to be told a new dirty aspect of its mentality: Class of users. Tell us all then at once; tell each user which user class you want her/him to belong to.