prefer aria-, data- over css classes in element picker

[scarf005]

original URL (twitter)

as-is	to-be

due to css minifier and obfuscators, element picker often picks hashed css classes.
this has following disadvantages:

• it's vulnerable to hash changes.
• it's hard to understand cryptic filters

making the filter to prefer human-readable properties like aria-label and data-testid over css classes (like how id has higher precedence over classes) would make it easier to zap elements.

[gorhill]

The picker can't tell whether a class name is meaningful or just random hashes as a result of server-side compiler.

The solution is to provide more options for users to decide what should be used -- something I have entertained since a long while now, but this requires work. I had been thinking that for each entry there would be a collapsible/expandable list of checkboxes about which tag/class/names/attributes should be used for that entry.

[scarf005]

yeah, providing radio group would work well.