I used the example for filtering and highlighting of events.
If i attach the b-mark class to the events, crudManager triggers a sync, wich fails, because of server logic.
For me, it looks like a bug in scheduler 5.0.1. change of cls shouldn´t persisted.
This is the whole test case.
We include bryntum with script tag. So you should change the paths for the scheduler.umd.js and css to load scheduler.
BTW: Wich errors occure? I run the file in Edge and everything was fine.
It's not a bug. The field persists its change to the server and this is by design. If you just want to highlight certain events you can use the eventRenderer function and for cells renderer function.
Well the demo does what it's meant to do ..changes the event cls field values which makes the records dirty.
The approach it shows just doesn't fit your requirements as far as I see.
If you need another logic just use another options the API suggests:
1) make cls field not persisted to the server at all
I don´t want to render all tagged events again and again.
cls is a DOMClassList, so nothing in that property should persistet, because its only markup no data.
So i try to add persist:false to my model and hope this stops triggering sync.
Main problem i think is, that i had to change the model / data of that event. For hilighting i think setting a class to the HTML-Element is a better approach. Could i access that element?