Adam Shaw

This has been resolved in [v7.0.0-beta.3](https://github.com/fullcalendar/fullcalendar-workspace/releases/tag/v7.0.0-beta.3) Updated repro: https://codepen.io/arshaw/pen/gbYWjyw?editors=001

It's been further refined in [v7.0.0-beta.4](https://github.com/fullcalendar/fullcalendar-workspace/releases/tag/v7.0.0-beta.4) when using navLinks: https://codepen.io/arshaw/pen/wBwyqoZ?editors=001

I acknowledge the need for something like this. Probably a simple flag like [unselectAuto](https://fullcalendar.io/docs/unselectAuto), which can be toggled to `false` to keep the popover open. BTW, I've closed #4643 for...

Hi @sulian, when implementing multiple definitions for business hours, I simply did not extend that functionality to other options. I did not realize it would be demanded. Accepting this as...

PS- if you do `selectContraint: 'businessHours'` and businessHours has multiple definitions, it should work as intended. same as `eventConstraint`

@Rubenvanhoeyveld the enhanced functionality for selectConstraint/eventConstraint has NOT been implemented yet. I'm curious to see why businessHours isn't working the way you want. I have some theories. Would you be...

@Rubenvanhoeyveld this example might help: https://fullcalendar.io/docs/resource_data/businessHours-per-resource/

I'll try to explain the current behavior: - There's an internal date anchor point that gets pushed into the future/past as the user navigates. You can obtain it via `Calendar::getDate()`...

@kaiwenlau , thanks for this thorough bug report. I can see there's a bug.

Updated repro with v6.1.11 (still not fixed): https://codepen.io/arshaw/pen/ZEPZRbK?editors=0010 The bug is less severe than I originally thought. The calendar is trying its best to display 2 events max per day...