What are they clicking on? Can you show a simplified example that demonstrates the issue?
What it sounds like though, it they are clicking maybe an "a" element that has a "src" attribute set and you are reacting to a message on it, that you are not preventing default? On Sunday, November 6, 2016 at 8:08:04 PM UTC-7, dedo wrote: > > Help! This is driving me crazy ... > > I have Python/flask at the back end, Elm at front. The landing page is, > say, http://localhost:5000. > > My Html.App.program is set up with an init Cmd wrapped around a > > Http.get decoderA "localhost:5000/initialData" > > of back-end data, . That works fine, browser url stays at landing page. > > My user next clicks a button and triggers a Cmd with a different callback, > wrapped around > > Http.get decoderB "localhost:5000/nextData/bar" > > and this time the back-end call happens, the response comes back, the > correct Msg is invoked, the right *update* state transition happens, and > then -- spontaneously -- the URL bar goes to "localhost:5000/?" -- with the > question mark -- and a spurious GET is sent to the back end, resetting the > page to the initial. > > Any ideas appreciated! > -- 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.
