Rich web applications deserve more meaningful events than mere "click". Custom events have long been recommended, but you still had to listen to click to fire them off. Now you don't, let trigger.js take care of it. Just declare what you want the browser events to mean, right on your elements. And that, is just the beginning of what trigger can do...
$ dotnet add package triggerNo README available.