How to respond to view-events in a purist MVVM way depends on the MVVM framework you're using and the platform you're on. I'd suggest you look at how it's done for a click event on a button with the framework you're using, and the approach should be very similar. If you're using UWP, you can even use x:Bind to bind an event straight to a method and forwarding the event arguments to that method. Some MVVM frameworks often provides some sort of attached property that forwards the event to a method.
Having said that, I think the 100% purist MVVM approach is a waste of time, and many of the MVVM framework developers agree that avoiding code-behind for the sake of avoiding code-behind is taking MVVM too far with no real benefit. Code behind is ok, as long as it is view-specific code - so there's not really anything wrong with responding to a click event and forwarding the necessary arguments to your VM (I'd even argue it makes your code flow easier to follow). It's really no different than defining for instance an EventToCommand attached property or similar thing approach in XAML markup, as it's generating the exact same thing, and you still have the important separation of concerns.
