Yes, this is a known bug. While creating custom components with the native events onclick and onchange, the event that is not bound in the sample component is rendered as null.
You can refer to the following thread for more information with an example code snippet.
https://github.com/aspnet/AspNetCore/issues/10398 [Issue Resolved]
Share with