I just dug into what I think is essentially the same bug. My guess was that textfields were getting removed from the DOM and then firing their blur events up through the event mapping chain — which had been updated to match the new view tree structure. It's on my list to try to build a small example of the bug after my team gets through its next milestone.
In the meantime, I worked around this by making fairly aggressive use of Html.Keyed to prevent pieces of the DOM from being reused. Mark > On Dec 13, 2016, at 9:56 AM, Simon <[email protected]> wrote: > > Sorry about using the C word! > > I had an error several months ago (0.16/0.17) where the wrong data would be > attached to message, causing all sorts of weirdness. It happened after a > successful logon and as the App tried to redirect to the main view. I have a > vague feeling that in the end all I needed to do was update > elm-lang/virtual-dom. > > Anyway, it has come back. It has something to do with when the browser puts > in login information for you. I can create the error by deleting the > auto-input and inserting my password and clicking enter to submit. > > Then what I see in my logs is this message > > `User.SwitchGroup: Blur "password"` > > Whereas SwitchGroup has type `String -> Msg` and `Blur "password"` are > artefacts of the elm-form library that was used in the Login component and is > not used in the User one. > > Does this remind anyone of something they have experienced, solved, and > remembered how they solved it? > > -- > 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. -- 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.
