Code review comment for lp:~coreygoldberg/selenium-simple-test/native-to-synthesized

Looking at the bug description, it's quite clear that it's difficult to provide
support for native events, while synthesized events should be much better
supported since they just rely on javascript.

I've made a small investigation on this and it seems that the point of using
native events is that, because of security reasons, some actions might not be
allowed through javascript in forms, which I guess can potentially break a test
case that is working already.

Hence, I'd say that to avoid introducing any regression, it would be safer to
avoid using synthesized events from now on as a default. Alternatively, you
could expose that as a configuration for sst or provide a different test case
class that has some defaults that are considered unstable, so that test cases
have some time to migrate to the new defaults and check if the work for them.