You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an all-day and timed event in a different week.
Move the view to that week, so you can see the events. They should render properly.
Move back to the previous week.
Notice: that an all-day event with the duration of the whole view quickly shows (for less than a second) then disappears.
Notice: timed events shift to the left, losing their original position
Possible Solution (Not obligatory)
Non-ideal Fix
One approach would be to hide the issue from the user. This would involve adding an overlay over the calendar so the user doesn't see the events changing position. This overlay could be a loading spinner, or an animated skeleton.
This approach is non-ideal because it doesn't fix the root cause and decreases performance by requiring the UI to render an overlay and the grid
Ideal Fix
Another approach is to find a way to prevent this from happening in the first place. This would require us to skip the computation of an event's width/height/grid coordinates during a pending navigation.
Root Cause
When we change the week, CalendarView re-renders, triggering re-renders in all its component tree until reaching event components, which re-calculates their position and size.
Context
This makes the app feel less smooth and lowers the user's confidence in its performance and reliability.
The text was updated successfully, but these errors were encountered:
Prerequisites
Expected Behavior
Current Behavior
Look at the all-day row during week changes:
bug.demo.mov
Steps to Reproduce
Possible Solution (Not obligatory)
Non-ideal Fix
One approach would be to hide the issue from the user. This would involve adding an overlay over the calendar so the user doesn't see the events changing position. This overlay could be a loading spinner, or an animated skeleton.
This approach is non-ideal because it doesn't fix the root cause and decreases performance by requiring the UI to render an overlay and the grid
Ideal Fix
Another approach is to find a way to prevent this from happening in the first place. This would require us to skip the computation of an event's width/height/grid coordinates during a pending navigation.
Root Cause
When we change the week,
CalendarView
re-renders, triggering re-renders in all its component tree until reaching event components, which re-calculates their position and size.Context
This makes the app feel less smooth and lowers the user's confidence in its performance and reliability.
The text was updated successfully, but these errors were encountered: