I think this is the problem. selected <| k == selectedKey
I assume this sets a selected="true" or selected="false" attribute on the element. That's not how the selected attribute works. The mere appearance of an attribute called "selected" on an option makes that option selected and if there are multiple options with the "selected" attribute the last one wins. So, this might actually be a bug. Elm forces you to specify "selected True" or "selected False" which isn't right. Selected is a boolean attribute: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/option According to https://www.w3.org/TR/html5/infrastructure.html#boolean-attributes .. The presence of a boolean attribute on an element represents the true > value, and the absence of the attribute represents the false value. In other words, selected is a boolean attribute and its presence means it is truthy, and "selected False" will give unexpected behavior. Seems like a bug to me. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
