@onpointerenter and @onpointerleave not firing

[iownbey]

This code isn't working with Blazor Wasm .Net 5.0, even though it is clearly supposed to be supported in this list: https://docs.microsoft.com/en-us/aspnet/core/blazor/components/event-handling?view=aspnetcore-5.0#event-arguments

@page "/"

<h1>Event Testing</h1>

<p @onpointerenter="() => { pointerentered = true; }" @onpointerleave="() => { pointerentered = false; }" >Pointer Enter and Exit events!</p>
@if (pointerentered)
    {
        <p>Tooltip!</p>
    }

@code {
    bool pointerentered;
}

The text, "Tooltip!" should be appearing when the user cursor enters the paragraph, but it isn't. If you switch out the event with "onpointerover/out" or "onmouseover/out" it works.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[mfluehr]

I have this same problem.

[xevoryn]

Same problem here. But there is a catch. The event is fired when the object it is attached to is clicked. This corresponds directly to the specification of the event behaviour for touch input. What is genuinely not working is the event in sight of the onmouseenter behaviour.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.