About the documentation : docs.dhtmlx.com/scheduler/api__s … espan.html
After a lot of tests, I (think to) have finally understood that it was not possible to use deleteMarkedTimespan() by passing neither “days: new Date()” or “<start|end>_date: new Date()” if the timespan was created by passing days: [X,Y,Z].
If it is really the case that could be notice in documentation, as it is done for days/zones vs start/end on addMarkedTimespan(), with in plus the fact that “days: ” creation does not allow a “days: new Date()” deletion.
By the way, if it possible it would be great. For the moment I think about using a onBeforeViewChange() event (or another) to add markedTimespan “on real time” instead at startup.
What I want to do : be able to add markedTimespans on all days (0 to 6) with zones, but delete them for precise dates (I would add specific new markedTimespans fot theses precise dates).
2/ I think about something I see recently (without finding a solution, I will se later maybe) : when using markTimespan() on a day, the timespan cover the events if the timespan is added after the events were loaded (eg: markTimespan + scheduler.updateView();)