Investigate inconsistent dropdown form behaviour

[patritzenfeld]

currently, with formify (Nothing @SingleChoiceSelection), I'll get a dropdown where the value defaults to the first real value, and the None option is disabled:

I want it to default to None instead (the table is big so making it default to None makes it easy for students to see which dropdown they have not yet answered), but I also want the required check to take effect.

For this to work, perhaps what I need is just removing disabled from https://github.com/fmidue/flex-tasks/pull/222/changes#diff-26588820d6d6d6eb9930e0b89192489214299acf12c3b5043f1b362e02333b7bR774? what do you think ?

Originally posted by @horriblename in #222 (comment)

[patritzenfeld]

I wasn't able to recreate the issue with an MRE and Firefox yet. There might be something else that influences the form besides just the Formify instance, e.g. other flex-tasks library code or even the OS somehow?

@horriblename can you send me the code (or a link to it if it has been pushed already) you have been using for the screenshots on Slack?

[horriblename]

I just tried it again on firefox, and it worked correctly, I must have did something wrong before, sorry about that!

[patritzenfeld]

I would guess the browser does some kind of autofill with previously remembered inputs if you reload the page. Otherwise I can't think of anything else that may cause this.