render as a function of {:dom-node ..} is not possible anymore, I'm quite sure.
a global dom-node function exists, but that takes the component as a first arg.
Calling dom-node in an event handler like here returns undefined (at least in a simplified test-case)
What does still work is rendering the things bound by letdom.
Given that refs have been introduced a while ago, I'd say we can quickly phase out letdom all together. Also, people collect the states of the two components in a common local or app-state anyway, and never access anything else than the .-target of an event handler.
The documentation of
letdom
is quite outdated, but in particular states that one could access 'bound' dom element in its 'own' event handler:{:dom-node ..}
is not possible anymore, I'm quite sure.dom-node
function exists, but that takes the component as a first arg.dom-node
in an event handler like here returnsundefined
(at least in a simplified test-case) What does still work is rendering the things bound byletdom
.Given that
refs
have been introduced a while ago, I'd say we can quickly phase outletdom
all together. Also, people collect the states of the two components in a common local or app-state anyway, and never access anything else than the.-target
of an event handler.