This PR solves #909, in which the second calendar appears with the wrong year and month when simultaneously using auto-range and multi-calendar features.
Upon investigation, I found that the year and month values were mistakenly assigned interchangeably in the handleNextCalendarAutoRange function, leading to the bug.
After fixing it, I confirmed that the second calendar showed the correct year and month.
This PR solves #909, in which the second calendar appears with the wrong year and month when simultaneously using auto-range and multi-calendar features.
Upon investigation, I found that the year and month values were mistakenly assigned interchangeably in the
handleNextCalendarAutoRange
function, leading to the bug.After fixing it, I confirmed that the second calendar showed the correct year and month.