Witold, could you put together a minimal Elm app + Selenium script that reproduces the problem? This might be a significant issue, since it would impact the possibility to end-to-end test Elm apps.
On Sun, Apr 30, 2017 at 8:28 AM, Witold Szczerba <witoldsz....@gmail.com> wrote: > This was my case with Selenium WebDriver and Chrome. The end-to-end tests > of my Elm application are failing because of this. > It was reported back in 2014: https://github.com/elm- > lang/elm-compiler/issues/835 > The issue is closed, but the bug is still present. > > You want to know my workaround? It "just-works" on Firefox, so this is the > browser I use for e2e tests… > > On Sat, Apr 29, 2017 at 11:57 PM, Francesco Orsenigo < > francesco.orsen...@gmail.com> wrote: > >> This is an interesting problem and I wonder if it would happen also with >> some other form of automated input (say, selenium). >> >> It might very well be a problem with Elm. >> >> >> >> On Saturday, April 29, 2017 at 12:51:48 AM UTC+10, Chris Van Vranken >> wrote: >>> >>> I'm using a barcode scanner to enter data into an elm textfield. The >>> barcode scanner basically works like a keyboard with a user that makes very >>> rapid keystrokes. This rapid entry causes random characters to be missing >>> in the textfield. If the scan is supposed to enter "50494'', one or more >>> of these characters will often be missing. Using the debugger I see that >>> my model has values for that field that change from "5" to "50" to "504" to >>> "509" to "5094", but it should be "5" to "50" to "504" to "5049" to >>> "50494" So it ends up replacing "504" with "509" instead of with "5049". >>> I believe this is a threading issue where two events are firing in parallel >>> instead of in sequence, and both events are starting with the same model >>> data ("50") with the output of one event replacing the output of the other, >>> when instead the output model for one event should be the input for the >>> next event. Is this a bug in Elm? How do I fix this? >>> >>> Thanks, >>> Chris >>> >> -- >> 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 elm-discuss+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Elm Discuss" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/elm-discuss/Oy35n_BHUGM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > elm-discuss+unsubscr...@googlegroups.com. > 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
