Blazor custom onclick event

[Kebechet]

Blazor @onclick event has different behavior on each platform.
E.g. on windows you can mousedown, hold for 5s, then mouseup and it will still trigger click event. On mobile devices if the press > ~500ms the event is not triggered.

I would like to unify all these things so that all of them behave exactly the same(after 400ms it wont trigger the event).

Because of this I would like to override build in:
Microsoft.AspNetCore.COmponets.Web.EventHandlers.onclick
with my custom
Blazor.EventHandlers.LongPress.EventHandlers.onclick

Currently I am getting an error:

Question:
I it even possbile to override the functionality ?
If so, how should I proceeed ?

Thank you

[javiercn]

@Kebechet thanks for contacting us.

That's likely not Blazor specific but browser specific.

Long presses trigger different events depending on the platform and input method. On desktops, a long press typically fires the standard sequence of mouse events: mousedown, mouseup, and click—even if the press lasts several seconds. On mobile devices, however, a long press often triggers a contextmenu event instead, which may suppress the click event entirely. This discrepancy is due to how browsers interpret long presses as gestures for secondary actions like text selection or context menus.

In addition to mouse and touch events, modern browsers support pointer events (pointerdown, pointerup), which unify input across mouse, touch, and pen devices. These can be useful for consistent handling across platforms. However, no native “long-press” event exists in the DOM; it must be implemented manually using timers that measure the duration between press and release events.

You can use a custom event handler to normalize the behavior across platforms if that's what you want. See https://learn.microsoft.com/en-us/aspnet/core/blazor/components/event-handling?view=aspnetcore-9.0#custom-event-arguments for details.

[Kebechet]

@javiercn

I already worked with custom event handlers. I have
@onlongpress - https://github.com/Kebechet/Blazor.EventHandlers.LongPress
@onshortclick - https://github.com/Kebechet/Blazor.EventHandlers.ShortClick - custom JS code that behaves like I described above. It is triggered just in case the click < 400ms.

But using @onshortclick everywhere would mean all our devs should use it instead of @onclick so that we properly handle stopPropagation. And some 3rd party components can still internally use @onclick and thus the propagation would not be respected correctly.

I would like to just override the blazor part. So that blazor built-in event handler onclick is triggered not by JS onclick event but by our shortclick event.

Is this override somehow possible ?

[dotnet-policy-service]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.