When tracking change events on a <select />, it would be nice to indicate what the value is of the select.
Apparently the :checked selector may work:
Add support for <form> elements
So why didn't you use :checked?
The problem with the current approach is that password values are put in a querySelector string. Are you sure this makes sense? (It definitely doesn't for my use cases). Perhaps it can be suppressed when the tagName is password?
Can you recreate this as an issue? The use-case was for tracking which item was selected, so you could copy-paste the selector in the same page yourself & re-produce what the user saw/clicked/etc.
The password example makes sense. I think there are different selectors that make sense for different tags.
I can see where it makes sense. And a value is more readable than an nth-child. I'm just worried about those cases where value is user input (textarea, text, password, and all the new types like email, etc). I'll open an issue.