The three seconds close wasn’t added by this ticket.

Ah!! I see it now testing with r11.

The behavior before was the same - 3 seconds to close, but the timeout was only applied to the last one in case I clicked more than one time.

But also testing in master is right, the behavior is now inconsistent, the timeout changes and the context menu is closed really fast sometimes. It feels like the 3 seconds are applied to the first menu, but if you click fast to open another two or three, after that the timeout is set too short, like less than one second for any other context menu that you open, and after some time it stabilizes again and set it to three seconds.

Definitely there is something non user friendly here, because the timeout becomes very short.

I think there is no need to make it a SysConfig - let’s keep it in three seconds (it can be customized in themes).

But I think is better to review why the timeout is getting shorter with more clicks.

hi , I’m aware with the three second timeout. if you click really fast, sometimes it will close before three seconds. currently the context menu will automatically hide after three seconds or user click again. but if user click faster, the timeout not gonna reset and will close the new context menu before three seconds. will be update to reset the timeout if user open new context menu. should we add the timeout to 5? or add the sys config to make it dynamically?

The three seconds close wasn’t added by this ticket.

Hi and

I just tested this and I see that the context menu is closed after three seconds, it doesn’t matter if the user is selecting the option. I mean, for a “slow” user the effect can be very unfriendly, the user click on the link, the menu is shown, the user goes to select the desired option and if not done within three seconds then the menu is gone.

Could it be a better way? Like closing the menu when the user click elsewhere in the screen?