These are chat archives for canjs/canjs

1st
Feb 2018
Gregg Roemhildt
@roemhildtg
Feb 01 2018 14:05
@phillipskevin I traced the can-dom-data-state 0.2 package version up the line...it looks like can-event@3.7.6 is the cause in my project. I'm importing "can-event" to add disptach event functionality to some view models
Kevin Phillips
@phillipskevin
Feb 01 2018 15:15
checkout the "Replacements for can-event" section of https://canjs.github.io/next/doc/migrate-4.html
Gregg Roemhildt
@roemhildtg
Feb 01 2018 15:19
Thanks!
Gregg Roemhildt
@roemhildtg
Feb 01 2018 15:29
Okay, I see component.events.inserted is removed, does that mean that stache on:inserted="dostuff()" is removed also?
Gregg Roemhildt
@roemhildtg
Feb 01 2018 15:41
I'm using on:inserted to initialize third party plugins, like date-picker on an element
Kevin Phillips
@phillipskevin
Feb 01 2018 15:46
yes, but you can add it back
with the can-3-4-compat code that's given there
Gregg Roemhildt
@roemhildtg
Feb 01 2018 15:49
Okay.
RyanMilligan
@RyanMilligan
Feb 01 2018 17:47
We're having an issue with the can-control-processor-capture module, which adds a "capture" processor to can.Control.processors that lets you subscribe to events in the capture phase. This was working fine in can 2, but no longer works after the upgrade to can 3.
The event selector is "{document} click capture", and this is not causing can.Control.processors.capture to be called anymore. Did something change there?