Hi,

First of all: does this bug still occur on your side ?

SOGo Connector makes no use of XPathResult therefore I don't know what happens here. Of course, I have not tested yet and I cannot currently since the zindus extension triggers an exception in my environment.

On the other hand, looking at the code of Zinduz there is namespace pollution there too. We attempt to avoid thisby prefixing our functions and objects with "SC" but there is never any guarantee....

I suspect that if you install the zindus addon into a new profile, or uninstall the SOGO addon from your current profile, you may find that it does not trigger an exception.

The zindus addon inserts exactly one name into the global namespace: ZindusScopeRegistry. The rest of the addon lives within that namespace. Whereas with the sogo addon, many, many functions are in the global namespace.

I only filed this bug because a user complained when they tried to use the two addons together. If you have found in your testing that they are still incompatible then I suspect the problem remains, namely that the sogo connector is polluting the global namespace.

Why the problem manifested with XPathResult I can't say. However if you have found that the zindus addon is still triggering an exception it may give you a clue on how to reproduce the problem without the zindus addon. ie with a test case involving just the sogo connector and a little javascript snippet that you can copy/paste into the error console (leaving the zindus addon out of it).