Where did this happen?
Hosted (compasscalendar.com)
Expected Behavior
If the user presses down on a calendar event and does not move the mouse while holding it down, the cursor should transition to move and the event should transition to become a placeholder. In other words, it should work like in Google Calendar.
Current Behavior
Cursor stays a default
Steps to Reproduce
- Create an event
- Mouse down on event
- Hold mouse down long enough for cursor to change
- Cursor does not change
Possible Solution
No response
Context
Related to #229
The current UX attempts to handle this situation as a "click" from the user's perspective. However, it's not a click — it's a drag. The user moused down, waited long enough for the cursor to change from default to move and then moused up without changing the times. This should be handled like any other drag event, where the form does not open afterwards. Behind the scenes, we might consider diffing and returning early if there was no change to the start dates to avoid an API call.
Where did this happen?
Hosted (compasscalendar.com)
Expected Behavior
If the user presses down on a calendar event and does not move the mouse while holding it down, the cursor should transition to
moveand the event should transition to become a placeholder. In other words, it should work like in Google Calendar.Current Behavior
Cursor stays a
defaultSteps to Reproduce
Possible Solution
No response
Context
Related to #229
The current UX attempts to handle this situation as a "click" from the user's perspective. However, it's not a click — it's a drag. The user moused down, waited long enough for the cursor to change from
defaulttomoveand then moused up without changing the times. This should be handled like any other drag event, where the form does not open afterwards. Behind the scenes, we might consider diffing and returning early if there was no change to the start dates to avoid an API call.