This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-15
Channels
- # announcements (1)
- # asami (29)
- # babashka (31)
- # beginners (48)
- # calva (39)
- # cljsrn (4)
- # clojure (56)
- # clojure-dev (51)
- # clojure-doc (3)
- # clojure-europe (40)
- # clojure-gamedev (13)
- # clojure-italy (22)
- # clojure-nl (3)
- # clojure-uk (5)
- # cursive (9)
- # datomic (184)
- # events (7)
- # fulcro (8)
- # graalvm (2)
- # jobs (1)
- # malli (6)
- # meander (1)
- # nrepl (5)
- # off-topic (10)
- # pathom (9)
- # polylith (33)
- # portal (2)
- # re-frame (7)
- # reagent (12)
- # releases (3)
- # remote-jobs (3)
- # reveal (27)
- # shadow-cljs (34)
- # sql (1)
- # vim (7)
- # xtdb (62)
Finding lately that putting on a tech talk in the morning helps me wake my brain up. Anyone have a handy list of "must watch" videos for Clojurians?
Not exactly a list, but here have a few https://github.com/matthiasn/talk-transcripts some that are off the list: • https://www.youtube.com/watch?v=epT1xgxSpFU • https://www.youtube.com/watch?v=eDad1pvwX34
I know the feeling, likely will watch some strange loop next days, https://youtube.com/playlist?list=PLcGKfGEEONaBjSfQaSiU9yQsjPxxDQyV8
Can chrome give me some feedback of what logic was triggered when i click something on browser page? I see a "event listeners" tab under "elements" which seems close in nature to what i would want. E.g "mouse" > mouse down ... But i would want to see the event log of fired events and which event listeners were triggered. Sort of like re-frame-10x
Short answer: no.
Long~ish answer: there's only one event handler for a specific event, ever. So if you have onMouseDown
, it's a single handler. Some libraries like jQuery create a queue of events, but that's completely on the library side - for the browser, there's only one event.
What happens is that sometimes an event "bubbles" - like, you click a div
. There's no handler, so the browser asks for the div's parent to handle. There's no handler either, so it keeps bubbling until it finds the handler.
So, in the first case: you'll only have a single event handler, so that's what Chrome will show you. On the second case: you'll have to monitor every parent to see if it have the handler, so it's not that helpful most of the time
Might not be exactly what you’re looking for but there is this https://playwright.dev/java/docs/cli#generate-code Also playwright has a bunch of other logging and tracing tools which might interest you.