Word of praise: Guys, I love Open Source I love your project & I love that you once again demonstrate the world the power of OSS ❤️ 🚀
Summary
This is issue is probably related to #47 #78 #97 #1271 and possibly #1269 .
As described in the title, I conntected my personal calendar via CalDav from a NextCloud instance.
I booked all of January 24th as busy in said calendar & expected Cal to disallow scheduling any further events on this day
-> However, all of the time slots were still free.
I had even checked what the primary calendar was & in which calendar my events should be created in.
At first I suspected this was intentional behaviour. Then I connected my gmail calendar and replayed the scenario
-> Events created in my gmail calendar blocked available time slots in Cal -> As expected!
Demonstration
Snippet of the personal CalDav calendar, note the busy scheduling

Availability displayed in Cal

Steps to Reproduce
- Connect your calendar via CalDav (mine is pulled from NextCloud) or from Apple (refering to words from my colleague)
- Schedule some events in your personal calendar that should not be available for booking via Cal
- Open your booking page & take note that those slots are still available
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Technical details
- Browser version:
- Node.js version
- Further information
- The german environment of NextCloud couldn't be an issue, right? Like the NextCloud API returning "beschäftigt" instead of "busy", right?
(The time zones between CalDav & Cal match)
Even further observation
Interestingly enough when I created a specific event at 3pm in my personal calender and double booked an event at this via Cal,
the newly created event is displayed as 3pm in the calendar, but says 2pm when I click on it.
Word of praise: Guys, I love Open Source I love your project & I love that you once again demonstrate the world the power of OSS ❤️ 🚀
Summary
This is issue is probably related to #47 #78 #97 #1271 and possibly #1269 .
As described in the title, I conntected my personal calendar via CalDav from a NextCloud instance.
I booked all of January 24th as busy in said calendar & expected Cal to disallow scheduling any further events on this day
-> However, all of the time slots were still free.
I had even checked what the primary calendar was & in which calendar my events should be created in.
At first I suspected this was intentional behaviour. Then I connected my gmail calendar and replayed the scenario
-> Events created in my gmail calendar blocked available time slots in Cal -> As expected!
Demonstration
Snippet of the personal CalDav calendar, note the busy scheduling

Availability displayed in Cal

Steps to Reproduce
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Technical details
(The time zones between CalDav & Cal match)
Even further observation
Interestingly enough when I created a specific event at 3pm in my personal calender and double booked an event at this via Cal,
the newly created event is displayed as 3pm in the calendar, but says 2pm when I click on it.