There's some interesting stuff that I'd like to add regarding events.

All driver events

• element clicked
• Navigated
• ValueChanged

This could be used in other things alongside with a method that would start listening user action and build Selenium Powershell output based on events that occurred.

It kind of ties in with #84 but in some way better because you could do it all from the module.

I can see some additional uses from things like FindElementCompleted to allow the possibility to calculate the amount of time multiple elements appear on the page (To measure performance )

https://www.selenium.dev/selenium/docs/api/dotnet/html/N_OpenQA_Selenium_Support_Events.htm