iCal alignment of the calendar
paul at thunderbird.net
Fri Jun 5 15:27:17 UTC 2020
Agreed that we are for closer adherence to standards. Once the
jscalendar standard is in use we'll have to deal with supporting it
along with iCal, which will be its own set of issues, but that's down
the road, so no reason not to more closely follow the iCal standard
Of the issues you list, "Tasks with a date without a time" seems fairly
straight forward. I would suggest starting with that one.
"Privacy Statuses" is a little trickier since apparently selecting
"Public", "Confidential" (or the current "Show Time and Date Only"), or
"Private" may mean different things depending on the server's settings.
>From a UX perspective it would be good, if possible, for the user to
know what they are choosing as they are choosing it. I'd like to
explore some of our options there.
So Max, you are proposing changing the option in the UI from "Show Time
and Date Only" to "Confidential". That means a user will need to know
the difference between "Confidential" and "Private". As you says this
is not exactly self-explanatory, so I would want to think about ways to
make this a bit more user friendly, as we are making the change to
follow the standard.
Thanks Max for raising these questions and for your interest in working
on these issues!
On 6/4/20 6:20 PM, Max Emig wrote:
> Hi all,
> I was looking into various issues that affect my experience of using
> Thunderbird for tasks and events with iCal/CalDAV drastically. I found
> some quite old neglected bugs assigned to it.
> It all boils down to interoperability issues between iCal RFC5545
> compliance and the current state of the user interface which users are
> familiar with as well as the possibility of other standards
> like draft-ietf-calext-jscalendar.
> In the following table, I am only pointing out the differences that
> are visible to the end-user and thus cannot be converted seamlessly:
> *Topic* *Current state of Thunderbird* *iCal RFC5545*
> *draft-ietf-calext-jscalendar* *Bugzilla*
> *All-day-events* All-day events are supported with temporarily
> storing time during selection in the dialog but saving without Saving
> the date(s) without time Time can be hidden from the overview but has
> to be saved. n/a
> *Tasks with a date without a time* Tasks with a date without a time
> are not supported, but are untouched when importing and then exporting
> them Saving the date(s) without time No example is given. Time can
> be hidden from the overview but has to be saved. 357502
> *Privacy statuses* Default: No value
> Available options: "Public Event", "Show Time and Date Only", "Private
> Event" Default: "Public"
> Available options: "Public", "Confidential", "Private"
> The server governs sharing based on this value and its settings.
> Default: "Public"
> Available options: "Public", "Private", "Secret"
> The standard governs which values may be shared under which
> conditions. 649944 <https://bugzilla.mozilla.org/show_bug.cgi?id=649944>
> I suggest stricter alignment to iCal RFC5545 at least in these cases
> to achieve full compliance. It is the only currently supported data
> format for tasks and events because the entire calendar is based
> on the iCal implementation libical or its new successor ical.js.
> The change from "Show Time and Date Only" to "Confidential" should be
> addressed in the changelog. Furthermore, a help article for the
> Privacy selector would be useful in any case as the concept of telling
> the server your preference on sharing is not exactly self-explanatory.
> tb-planning mailing list
> tb-planning at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tb-planning