Maybe your js code acts too early, when there is no element yet in the DOM?
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss...@googlegroups.com.
Perhaps Elm is re-rendering the element on which you've attached the event, thus removing the event? I haven't yet used the Html.Keyed library, but I understand it can be helpful in cases like this where you want to keep the same DOM element around, since it has state attached to it.
On Fri, Sep 30, 2016 at 1:01 AM, Witold Szczerba <witold...@gmail.com> wrote:
Maybe your js code acts too early, when there is no element yet in the DOM?
30.09.2016 8:35 AM "Timothy Williams" <t.will...@gmail.com> napisał(a):
I have this elm-html element:--Html.a [href "#menu-toggle", class "btn btn-default", id "menu-toggle" ][ text "Toggle Menu" ]which is a direct translation from:<a href="#menu-toggle" class="btn btn-default" id="menu-toggle">Toggle Menu</a>and shows up in the browser as:<a href="#menu-toggle" class="btn btn-default" id="menu-toggle">Toggle Menu</a>But the same javascript that works on the html doesn't work on the elm code:$("#menu-toggle").click(function(e) {e.preventDefault();$("#wrapper").toggleClass("toggled");});Is plain js/jquery unable to interact with elm elements as it would with html elements?
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...@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...@googlegroups.com.
Perhaps Elm is re-rendering the element on which you've attached the event, thus removing the event? I haven't yet used the Html.Keyed library, but I understand it can be helpful in cases like this where you want to keep the same DOM element around, since it has state attached to it.
On Fri, Sep 30, 2016 at 1:01 AM, Witold Szczerba <witold...@gmail.com> wrote:
Maybe your js code acts too early, when there is no element yet in the DOM?
30.09.2016 8:35 AM "Timothy Williams" <t.will...@gmail.com> napisał(a):
I have this elm-html element:--Html.a [href "#menu-toggle", class "btn btn-default", id "menu-toggle" ][ text "Toggle Menu" ]which is a direct translation from:<a href="#menu-toggle" class="btn btn-default" id="menu-toggle">Toggle Menu</a>and shows up in the browser as:<a href="#menu-toggle" class="btn btn-default" id="menu-toggle">Toggle Menu</a>But the same javascript that works on the html doesn't work on the elm code:$("#menu-toggle").click(function(e) {e.preventDefault();$("#wrapper").toggleClass("toggled");});Is plain js/jquery unable to interact with elm elements as it would with html elements?
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...@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...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscribe@googlegroups.com.