Currently a work in progress. Not all ActivatorContent has been inspected and replaced where necessary.
Additionally, the documentation should be expanded.
If the ActivationEvent is RightClick or MouseOver, calling context.OpenMenuAsync is not necessary, as these events are handled differently.

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

If the ActivationEvent is RightClick or MouseOver, calling context.OpenMenuAsync is not necessary, as these events are handled differently.

Small update:

@danielchalmers
MouseOver has special behavior in that it also supports onclick (not specifically left or right), i dont know if that's relevant
Hover opens it temporarily but Click opens it permanently

This means that you actually do need to call context.OpenMenuAsync or context.ToggleMenuAsync (depending on the behavior we want to achieve) when the ActivationEvent is MouseOver.

There are a few open topics:

1. Currently, on desktop, the behavior is such that if you hover over and click on the activation area while the mouse is hovering over it, the menu will toggle (close). If you click again on the activation area, the menu will open permanently, and you can hover out without it closing. The question is: should we change this behavior? Specifically, should we make it so that on non-touch devices, when you hover and click on the activation area, the menu will not toggle (close) but instead instantly activate the permanent mode?

2. Should we create a specially named method, such as context.OpenMouseOverMenuAsync? This would allow us to properly document what it does, making it less confusing for the end user to understand which context action to use.

The transient flag on OpenMenuAsync is what decides if it should stay open permanently or not. By default it's false and permanent, but if's true (set during the pointerenter handler) it closes if the pointer leaves.