Planning Calendar empty cell click outside current month does not fire event
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
What is the issue and how can we reproduce it?
- Open the sample PlanningCalendarMulti OR the Minimal example attached (I've added some Message boxes to help with debugging)
- On the top right corner select "1 Month" view
- Go to February 2017
- Click on empty cell for
John Millerthat is outside of the current month (February) -March 2, 2017 - The calendar view is moved to the next month - March, but
startDateChangeevent is NOT triggered
We need this event to be triggered with the correct getStartDate in order to load the relevant appointments data for the next month
Error:
The calendar view is moved to the next month - March, but
startDateChangeevent is NOT triggered
Expected behavior:
The calendar view is moved to the next month - March, and startDateChange event is triggered, and getStartDate method to have the correct date March 1, 2017
Minimal example
sap.m.sample.PlanningCalendarMultiFork.zip
Which OpenUI5 version is your project targeting?
1.146.0
Is the issue device- or browser-specific?
No, not browser specific
Confirmation
- I have searched the existing issues and reviewed the relevant documentation as well as the API reference.
- I am not disclosing any internal or sensitive information.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PlanningCalendarMulti sample and reproduce the February 2017 to March 2017 empty-cell click described in the issue. Trace the PlanningCalendar handling of the outside-month cell and verify that moving to March fires startDateChange with getStartDate set to March 1, 2017.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100