This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-05
Channels
- # announcements (1)
- # babashka (61)
- # babashka-sci-dev (1)
- # beginners (54)
- # biff (17)
- # cider (4)
- # circleci (1)
- # clj-commons (39)
- # clj-kondo (26)
- # cljdoc (40)
- # clojure (41)
- # clojure-europe (32)
- # clojure-norway (4)
- # clojure-portugal (1)
- # clojure-uk (2)
- # clojurescript (59)
- # clr (69)
- # conjure (7)
- # cursive (22)
- # data-science (16)
- # datalevin (1)
- # datomic (19)
- # docker (31)
- # funcool (1)
- # honeysql (6)
- # hoplon (1)
- # hyperfiddle (41)
- # introduce-yourself (1)
- # juxt (2)
- # leiningen (5)
- # nbb (14)
- # nextjournal (38)
- # off-topic (47)
- # polylith (2)
- # rdf (5)
- # re-frame (4)
- # reitit (27)
- # releases (6)
- # scittle (10)
- # shadow-cljs (24)
- # sql (11)
- # squint (1)
- # tools-build (33)
- # tree-sitter (4)
- # vim (39)
Hi there. I'm going through wonderful re-frame documentation currently looking at the explanation of the reframe /simple example with the coloured clock. I'm quite surprised that the dom doesn't apparently try to update until the user enters some valid colour in the input box. The browser doesn't update the dom unless the syntax is valid? https://day8.github.io/re-frame/dominoes-live/
I doubt this is behaviour specific to re-frame or Reagent. It seems to come all the way from React itself: https://stackoverflow.com/questions/63318740/react-passing-invalid-css-color-through-prop-does-not-affect-previously-stated
Seems it is the browser itself that only updates the property when it receives a valid value to update to. https://stackoverflow.com/questions/48484767/javascript-check-if-string-is-valid-css-color?noredirect=1&lq=1