This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-19
Channels
- # beginners (98)
- # boot (9)
- # business (2)
- # cljs-dev (10)
- # clojars (4)
- # clojure (36)
- # clojure-brasil (1)
- # clojure-dev (3)
- # clojure-poland (3)
- # clojure-russia (39)
- # clojure-spec (29)
- # clojure-uk (8)
- # clojurebridge (1)
- # clojurescript (70)
- # component (3)
- # cursive (2)
- # datomic (2)
- # figwheel (1)
- # hoplon (9)
- # klipse (29)
- # off-topic (7)
- # om (3)
- # onyx (11)
- # overtone (3)
- # rdf (1)
- # re-frame (18)
- # schema (1)
- # spacemacs (1)
- # untangled (5)
@thedavidmeister wow, TIL. always had just assumed call order would be respected
http://stackoverflow.com/a/28236904 looks like a nice solution
yeah, in JS you have to maintain your own explicit queues anywhere that race conditions might be undesirable ๐
@alandipert itโs what @micha did in https://github.com/hoplon/hoplon/pull/156/files
anyone know any reason why a div being added in an if-tpl
higher in the dom would make an input lose focus but not below?
wrapping the if-tpl
in another div
seemed to mitigate the issue
@thedavidmeister: it probably is caused by how the Dom determines what is part of the tree when removing the elements