NC Connector for Thunderbird not compatible with Thunderbird 147+

[slamp]

Hello,
The version published on https://addons.thunderbird.net/en-US/thunderbird/addon/nc4tb/ is not compatible with Thunderbird 147.0.1

[DeBaschdi]

Currently i can only Support Thunderbird ESR Versions
#3 (comment)

[slamp]

oh!
Sorry for the noob question, what is ESR ?
Is it an equivalent of Long Term Support (LTS) ?

[DeBaschdi]

Yes.
Exactly, in the future, I also want to be able to support the regular release channel.

[slamp]

Thanks. I will test Thunderbird ESR and NC connector.

[nextcloudfan]

Only the minority will use ESR versions. For good reasons. Please provide regular version support.

[DeBaschdi]

Thanks for the feedback. I agree that regular release support would be valuable, and I want to add it.

At the moment, NC Connector supports Thunderbird ESR as the stable baseline. I do not have public data showing that ESR is only a minority use case, and in managed environments ESR is still a common target.

The bigger blocker is not just the version number. Today, the add-on still needs a "small" custom experiment layer for calendar editor handling. The Talk button already uses Thunderbird’s standard "calendar_item_action" path, but Thunderbird does not yet provide the full deterministic editor-context contract I need across dialog and tab editors, especially for new and unsaved items.

Because of that, the add-on currently relies on a custom bridge for things like a stable editor identity ("editorId"), deterministic read/write access to the currently open editor ("getCurrent" / "updateCurrent"), and cleanup signals when an editor is saved, discarded, or superseded.

That extra experiment layer makes maintenance harder and increases the chance of breakage across Thunderbird updates.

To help move this forward, I already opened an upstream PR for Thunderbird’s calendar API:
thunderbird/webext-experiments#65

The goal is to move the missing editor-context pieces upstream so add-ons can work with open editors, including unsaved items, without custom experiments. My expectation is that regular release support becomes much more realistic once that API is available upstream.

So yes: regular release support is planned, but I would prefer to land it on top of an upstream API instead of growing more add-on-specific experiment code.

Testing reports for current Thunderbird release versions are still very welcome in the meantime.

[nextcloudfan]

How should we test on Thunderbird release? The add on is not compatible and can not be installed manually either.

[DeBaschdi]

How should we test on Thunderbird release? The add on is not compatible and can not be installed manually either.

As i Said before
#3 (comment)

[nextcloudfan]

As I said above...

[DeBaschdi]

Okay, so you already unpacked the XPI, edited the manifest.json, repacked it into an XPI, and then tried to install it, but it still does not work? In that case, please post the log messages from the Developer Console.

[DeBaschdi]

For regular Release Channel,
I will offer now MAINLINE Builds (pre-release)

Check Out the newest Version
https://github.com/nc-connector/NC_Connector_for_Thunderbird/releases/

Please Take Notice about TB >=153
#18 (comment)