This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-25
Channels
- # aleph (1)
- # beginners (72)
- # boot (3)
- # cider (28)
- # cljs-dev (193)
- # cljsrn (11)
- # clojure (73)
- # clojure-brasil (3)
- # clojure-gamedev (2)
- # clojure-russia (6)
- # clojure-spec (30)
- # clojure-uk (26)
- # clojured (1)
- # clojurescript (32)
- # code-reviews (9)
- # core-async (4)
- # datascript (5)
- # datomic (9)
- # dirac (38)
- # fulcro (23)
- # garden (11)
- # leiningen (1)
- # luminus (11)
- # lumo (6)
- # off-topic (17)
- # quil (2)
- # re-frame (2)
- # reagent (3)
- # ring (3)
- # shadow-cljs (12)
- # spacemacs (4)
- # sql (2)
- # unrepl (85)
- # vim (3)
@feihong.hsu I wouldn't expect any differences in dispatch
between those two templates, that would be a bug if so. I'd be very interested to see it if there was a difference. dispatch
ed events are handled asynchronously, the dispatch just adds it to the event queue, and tells re-frame to run the queue (0.1ms later) with goog.nexttick. dispatch-sync
is a way to synchronously call an event handler, so it will be handled in the same click event callback
Just to add to the complexity, Chrome has been doing some work on passing the call stack across asynchronous boundaries, including goog.nexttick, I'm not sure whether the permissions would carry across that callback as well.