[Calendar] Clicking anywhere in the Calendar triggers a click in another cell ever since upgrading to 3.33.0 and later (4.2.0 current latest version)

This looks like a regression of a bug that was fixed in 3.32.1 (incorrect args.cell.start/end in onTimeRangeSelect/onTimeRangeSelected events when heightSpec is set to "BusinessHoursNoScroll").

It should be fixed now in the latest sandbox build (NPM).

Please let me know if the problem persists.

This seems to have resolved the time selection issue (clicking no longer selects a time ~6 hours ahead). However, the reversed day selection in RTL is still a persisting issue.

I am aware that the lite version doesn’t explicitly support RTL and I know some calendar interactions do indeed still not work appropriately (and I am explicitly opting out from using them currently), but this is an interaction that has previously worked flawlessly for me up until 3.32.1 and I am therefore still unable to upgrade to the latest sandbox build because of this.

I tried updating to the new 4.2.1 version and I can confirm that the issue still partially persists. I tried testing on both 3.32.1 and 4.2.1 to confirm and double check.

When I click somewhere within the Calendar it will sometimes “remember” where I clicked previously and click there again even after clicking elsewhere several times. This does not happen in 3.32.1 no matter how many times I try and is somewhat common in 4.2.1.

In addition, there is still the matter of the regressing RTL issue. This was not present before. Whenever I click anywhere on the calendar in RTL the day selection uses the reversed day value (e.g. Sunday-Saturday, Monday-Friday etc.).

I would very much appreciate if both issues could be fixed so that I can safely update my version and use all of the new features provided.

Would you be able to create a sample project that reproduces the issue (you can generate a blank project using the UI Builder)? It looks like it might be related to a specific setup.

Your RTL setup is broken because of changes that were necessary for the snap-to-grid disabling. You’d have to wait for a proper RTL support that may come in the future.

Hi Dan,

I appreciate the update.

I’ll look into reproducing the issue and will post as soon as I manage to figure out what’s causing it.
In the meantime, if you would like, I can provide some insight into how I’m setting up the calendar as well as any surrounding details that may be relevant to the issue at hand.

For starters, here is how I have it set up in my react application:

            <DayPilotCalendar

              ref={calendarRef}

              headerDateFormat={calendarViewPortConfig.headerDateFormat}

              viewType={viewType === "Biweek" || viewType === "Month Calendar" ? "Days" : viewType as "Week" | "Day"}

              visible={viewType !== "Month"}

              days={viewType === "Biweek" ? 14 : 30}

              startDate={startDate}

              heightSpec='BusinessHoursNoScroll'

              businessBeginsHour={businessBeginsHour}

              businessEndsHour={businessEndsHour}

              timeFormat="Clock24Hours"

              // useEventBoxes={"Never"}

              // snapToGrid={true}

              events={events}

              timeRangeSelectedHandling="Enabled" onTimeRangeSelected={handleTimeRangeSelected}

              eventClickHandling="Enabled" onEventClick={handleEventClick}

              eventResizeHandling="Update" onEventResize={handleEventResize}

              eventMoveHandling="Disabled" onEventMove={handleEventMove}

              eventDeleteHandling='Update' onEventDelete={handleEventDelete}

              onBeforeEventRender={handleBeforeEventRender}

              onBeforeCellRender={(args: DayPilot.CalendarBeforeCellRenderArgs) => defineWeekendDays(args)}

              cellHeight={30}

              hourWidth={50}

              durationBarVisible={false}

              theme="calendar_default"

              locale={locale}

            />