This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-16
Channels
- # bangalore-clj (8)
- # beginners (78)
- # boot (68)
- # cljs-dev (32)
- # cljsrn (43)
- # clojars (2)
- # clojure (147)
- # clojure-italy (4)
- # clojure-nl (2)
- # clojure-quebec (1)
- # clojure-russia (19)
- # clojure-spec (17)
- # clojure-uk (25)
- # clojurescript (98)
- # clr (2)
- # core-async (14)
- # cursive (5)
- # datascript (1)
- # datomic (23)
- # emacs (4)
- # hoplon (8)
- # jobs (4)
- # kekkonen (1)
- # lein-figwheel (9)
- # off-topic (2)
- # om (2)
- # om-next (9)
- # onyx (4)
- # planck (2)
- # re-frame (14)
- # ring-swagger (3)
- # untangled (18)
I was looking at the guide for integrating material components (https://github.com/material-components/material-components-web/blob/master/docs/integrating-into-frameworks.md#the-simple-approach-wrapping-mdc-web-vanilla-components) and it mentions that the wrapping component (e.g. like in hoplon) must call the material component’s .destroy()
to clean it up
Is it possible to register a hook in Hoplon for an element being removed from the DOM?
@piotrek not that I'm aware of but this has come up before
It might be possible without Hoplon via mutation observers, in some browsers at least
On the other hand I am wondering if it is even needed with those material components if I would include them directly in DOM
Yeah- if you had one in a loop TPL, they'd only be created and reused
And presumably you'd have the content and attributes that matters cell driven
@piotrek: I'll be updating material-hl to support material-components which are actually v2 of material design lite