Open Iharsh-Mishra opened 4 days ago
References: The original PR #242
https://datatracker.ietf.org/doc/html/rfc5545#section-3.2.9
https://icalendar.org/iCalendar-RFC-5545/3-2-9-free-busy-time-type.html
RFC5545 says about FBTYPE "If not specified on a property that allows this parameter, the default is BUSY." But then immediately gives an example:
FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z
That example specifies what is already the default.
In theory, clients should be happy to accept FREEBUSY
without FBTYPE
specified.
@Iharsh-Mishra @surajdadral did this problem start happening in a recent release of Thunderbird? Or has this been broken in Thunderbird for a long time?
@Iharsh-Mishra has this problem/bug been reported to Thunderbird?
If so, please provide a link to the bug report.
If not, then please report it to Thunderbird and link back to here.
Then we can see if Thunderbird is going to adjust its code to conform to the RFC.
References:
https://bugzilla.mozilla.org/show_bug.cgi?id=1931475
https://github.com/mozilla/releases-comm-central/issues/102
This is working fine in Thunderbird version 60.0
FREEBUSY:20241115T021500Z/20241115T051500Z
For thunderbird versions above 68.0 it is not working.
https://bugzilla-dev.allizom.org/show_bug.cgi?id=1853385
This is a test instance of Bugzilla and not to be used for any production purposes.
My bad. Now I have updated the link.
I'd also say that if you want this bug to be fixed, it will probably really help them to include more details on what's wrong (FBTYPE=BUSY
seems to be required, even though it's the default value) a link to the related standard, maybe include some example data and perhaps even a link back here. Also point out this is a regression.
Because if someone picks up on this ticket this is potentially an easy fix. But if they have to install sabre/dav and reproduce this suddenly could be a bigger task. Also FYI Thunderbird's calendar code is probably mostly Javascript so it may not be that hard to contribute this change either. Just putting it out there!
So in file
lib/FreeBusyGenerator.php
there was a code added by @evert on line number 591Related Commit
This caused freebusy in Thunderbird not working. For status that are BUSY the response doesn't contain FBTYPE which results to No Information status in Thunderbird.
Right now the response that I am getting, which resulted in Thunderbird showing No Information status of FreeBusy, is like:
But Thunderbird wants this, (to show correct BUSY status):
Reverting the code change will make FreeBusy status work in Thunderbird.
My ThunderBird version is 128.4.1 My sabre/dav version is 4.7 My machine is ubuntu 22.04