Flyouts assigned to a button inherit the "hand" cursor
drasticactions opened this issue · 1 comments
Describe the bug
We had an issue filed by a customer concerning Flyouts and how they propagate their cursors. For example, if you assign a flyout from a button, the cursor in the flyout inherits the "hand" cursor from the button.
This is expected behavior; pop-ups inherit all properties from the object where they're displayed. If you wish to change this behavior, you can override the template (Globally or by object) to adjust it. There is a good argument to change this behavior to default to the "cursor" cursor instead for Flyouts, but this would now be breaking behavior from what has existed in the past. That could result in other people coming to complain about needing to change code they haven't needed to in the past.
This issue is here to track what we can or should do about it. At least, we can document this behavior specifically for Flyouts/Buttons and document how to override it. We can also change it globally to always default to cursors, but this may be too drastic a change, at least for v11.
To Reproduce
Create a button with a flyout and look at the cursor.
Expected behavior
No response
Avalonia version
11.x
OS
No response
Additional context
No response
Original behavior looks more like a bug, same with textbox menu inheriting IBeam cursor. That was fixed with a very nasty style in template.