Hello Steve,

The array should be updated immediately when a checkbox is selected and the UI is updated after that. Here is a JSBin example which shows that the array is updated accordingly to the selection which was made.

http://jsbin.com/igirur/2/edit

Regards,
Petur Subev
the Telerik team

Try this one instead: http://jsbin.com/igirur/4/edit

Hello Steve,

I am not sure I understand the question, can you please explain in more details what exactly is the issue with the example you shared?


Kind Regards,
Petur Subev
the Telerik team

OH!...I assume you tried it in chrome and it's fine

..try Firefox

Hello Steve,

The order of the events being triggered is different.

Same is happening here try with different browsers again:

http://jsbin.com/anafev/2/edit

Kind Regards,
Petur Subev
the Telerik team

I know, I'm not exactly sure what you're telling me here...I'm reporting the one reporting the events are firing at different times on different browsers?

Hello Steve,

There is not any kendo code in this example and the events are fired in different order. And since Kendo depends on the order in which the events are fired, Kendo will behave the same way as the events are fired.

There is nothing we can do to change the order of the events in the different browsers.

All the best,
Petur Subev
the Telerik team

There's no way for kendo to account for this...not even file something with mozilla...orr....anything, I'm just screwed here?

Hello again Steve,

As I already replied in my previous post I am sorry but there is nothing we can do.

Regards,
Petur Subev
the Telerik team

Is this still the case?  If so wow!  So in Chrome, the click event's reading of the bound vm value is the original value, then after the click finishes the binding is updated to the new value.  Yet in IE, the binding update is made prior to the click event.  Fascinating!  

What is the best way to read the desired value during the click event, something of the parameter, I'll call 'e'?

Hello Keith,

As Petur has explained previously, the Kendo implementation depends on the browser event sequence. If the different browsers follow different sequence for those events (Chrome and Firefox vs IE and Edge), there is nothing much we can do.

As per the scenario that has been previously discussed, an ugly (but working) workaround would be to timeout the execution of the logic in the click handler. This way, the value will be changed accordingly independent from the event sequence:

Here you will find a sample Dojo implementing the above.

Regards,
Veselin Tsvetanov
Progress Telerik