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
When configuring a Custom Screen calendar block with a URL (e.g., Apple iCloud, or iCal/ICS Link, etc.) that is invalid or otherwise fails, properly puts it into "invalid" state and shows an the exclamation icon with an error tooltip. However, changing the URL to correct it and re-saving inadvertently leaves the "enabled" state of that calendar entry "off"/disabled. This then requires a second calendar block edit to turn on the "enabled" checkbox and save again.
This required second-edit may be apparent if there are no other valid calendars configured and it actually states "No calendars have been enabled", but if there are valid calendar entries, the user may not notice the problem, or may wonder why their calendar is still not showing up.
An improved design will have to be considered to have corrected entries re-enable themselves in this type of scenario.
The text was updated successfully, but these errors were encountered:
When configuring a Custom Screen calendar block with a URL (e.g., Apple iCloud, or iCal/ICS Link, etc.) that is invalid or otherwise fails, properly puts it into "invalid" state and shows an the exclamation icon with an error tooltip. However, changing the URL to correct it and re-saving inadvertently leaves the "enabled" state of that calendar entry "off"/disabled. This then requires a second calendar block edit to turn on the "enabled" checkbox and save again.
This required second-edit may be apparent if there are no other valid calendars configured and it actually states "No calendars have been enabled", but if there are valid calendar entries, the user may not notice the problem, or may wonder why their calendar is still not showing up.
An improved design will have to be considered to have corrected entries re-enable themselves in this type of scenario.
The text was updated successfully, but these errors were encountered: