Calling hooks after inserting into the dom?

At the moment, the behaviour of virtual-dom is to call hook on a hook once the dom element for the respective vnode has been created. However, if the dom element is newly created it has not yet been inserted into the dom, so has not been laid out and doesn’t have width or height properties. In order to make a basic hook that reads the width of a vnode once rendered you are forced to use a timeout like so:

hook: (element) ->
  # defer reading the width until the element has been inserted into the dom
  setTimeout ->
    width = $(element).outerWidth()
    # do something with width
  , 0

And deal with a whole load of dodgy asynchronicity (which makes testing hooks especially annoying). Is there a particular reason for this behaviour, or could we change it so that hook is called after insertion into the dom, avoiding the need to use timeouts in cases like the above?

[wclr]

+1 In cyclejs you can use CycleDOM’s observable API to know that element added to the dom. But think this is needed really for v-dom hooks/widgets eigher.

[udp]

+1

Ran into this trying to use codemirror as a widget and had to use the setTimeout 0 hack.