CalDAV, Thunderbird and tasks that last "all day"

[wehkah]

Hello,

for quite a long time now I noticed a problem affecting tasks that are marked as "all day" (= without a specific time): whenever Thunderbird/Lightning is involved, the mark "all day" is lost and due time of such a task is set to midnight. This will cause Android calendars to fire up an alarm in the middle of the night.

I have worked with many CalDAV clients and with many CalDAV servers, and I can definitely pin this misbehaviour down to TB/Lightning. I've had long discussions on TB help forums before, I filled bug reports, but still a solution is not to be seen in the near future.

I know that this forum is not meant to be a place for complaining about other people's software, and this comment is not meant to be that way. I'd just like to ask two questions to this community / forum:

1. Can anyone else confirm this behaviour, is anyone else suffering from it?
2. Is there any kind of chance that Radical could do something against this loss of the mark "all day", e.g. a special treatment of task that are uploaded / downloaded by TB+Lightning?

I am asking these questions here, because there are people reading this forum who really know the internal structures of CalDAV data and who know how to code a CalDAV server and who might have an idea of what is causing this problem.

[pbiering]

Is there any kind of chance that Radical could do something against this loss of the mark "all day", e.g. a special treatment of task that are uploaded / downloaded by TB+Lightning?

There is currently no feature inside Radicale to adjust content provided by clients on-the-fly before storing or adjust-before-handout on request.

[wehkah]

Actually, I think I might have spoken too soon! It seems in latest releases of Betterbird this error has been fixed - at least, after more then a decade! BB version 140.x and Radicale 3 seem to work well together, and until now the "all day" mark is preserved when synching. Keep fingers crossed! :)