Closed Bug 1718542 Opened 3 years ago Closed 3 years ago

cal.itip no longer uses calendar's transport

Categories

(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)

Thunderbird 90
defect

Tracking

(thunderbird_esr78 unaffected, thunderbird90 affected)

RESOLVED FIXED
91 Branch
Tracking Status
thunderbird_esr78 --- unaffected
thunderbird90 --- affected

People

(Reporter: neil, Assigned: neil)

References

(Regression)

Details

Attachments

(1 file, 1 obsolete file)

The itip transport for an item is supposed to be retrieved by calling item.calendar.getProperty("itip.transport"). Bug 1710172 substituted that with cal.provider.getImipTransport(item.calendar), however that's actually a utility function for calendar providers to call as part of their handling of the getProperty call.

(Edit: Ugh, I always get imip and itip confused. Sigh...)

Attached patch Proposed patch (obsolete) — — Splinter Review
Attachment #9229196 - Flags: review?(geoff)
Attached patch Fixed bug and test — — Splinter Review

... the test wasn't even providing the transport correctly...

Attachment #9229196 - Attachment is obsolete: true
Attachment #9229196 - Flags: review?(geoff)
Attachment #9229197 - Flags: review?(geoff)
Attachment #9229197 - Attachment is patch: true

Hello.
What's the intended effect here, seeing as getProperty("itip.transport") calls calprovider.getImipTransport()? Am I missing something?
It seemed to me that configuring the transport of a calendar is a feature not quite implemented.

Status: NEW → ASSIGNED

Thunderbird 90 is affected

Flags: needinfo?(mkmelin+mozilla)
Attachment #9229197 - Attachment description: Fixed test → Fixed bug and test

Lasana wrote in comment 3:

Am I missing something?

Other calendar providers, which might need a different implementation. You've basically hardcoded one implementation, making other implementations impossible.

(In reply to Ben Bucksch (:BenB) from comment #5)

Lasana wrote in comment 3:

Am I missing something?

Other calendar providers, which might need a different implementation. You've basically hardcoded one implementation, making other implementations impossible.

Thanks for the reply. Other providers from where, extensions?

Yes, there are many calendar providers.

Flags: needinfo?(mkmelin+mozilla)

Comment on attachment 9229197 [details] [diff] [review]
Fixed bug and test

This should be OK. I'm not too familiar with the extension infrastructure but if they can register additional providers it makes sense.

Attachment #9229197 - Flags: review+
Attachment #9229197 - Flags: review?(geoff) → review+

Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/097aa8f960e2
Fetch the itip.transport calendar property again. r=lasana,darktrojan

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: