I'll check this scenario soon and get back to you.
Support Forum
Search found 2320 matches
I don't really observe the behavior you are describing. See the video here: https://streamable.com/02otz1
Perhaps you have some Chrome plugins?
If I'm correct it was fixed in 5.6.5 as part of this ticket: https://github.com/bryntum/support/issues/8079
@dominicdolan What version of our component do you use? IIRC we've fixed this issue recently, please try to reproduce with the latest code?
Ah, reproduced now, thanks for the clarifications. We'll be fixing it soon.
@lucacervo98 Hi, this issue does not seem to be reproducible? (see the video I posted in the ticket)
The exception says - some asynchronous calculation was attempted to be performed in the synchronous context. This is usually a bug, to tell more I need to be able to reproduce this, please provide a test case if possible.
@lanpeng Hi, it seems this issue has been already fixed - see the video I've uploaded into the ticket. Please try reproducing it with the latest version of our code and let me know?
Hi,
You can provide a startDate : new Date()
config for the scheduler during instantiation. This will disable the calculation of earliest date and match the old behavior for the case when no startDate
config was provided.