NoScript dev 2.4.2rc4 & SeaMonkey trunk with Sync

[OnTheRocks]

Hello!

I just realized a problem with NoScript (2.4.2rc4 but probably also older versions) with SeaMonkey trunk builds and the included Sync client. As long as NoScript is enabled Sync does not work anymore. After disabling NoScript in the Add-ons Manager Sync starts syncing data again.

Regards
OnTheRocks

[OnTheRocks]

I just realized a problem with NoScript (2.4.2rc4 but probably also older versions) with SeaMonkey trunk builds and the included Sync client. As long as NoScript is enabled Sync does not work anymore. After disabling NoScript in the Add-ons Manager Sync starts syncing data again.

I forgot to mention that there is no message in the error console when I add a bookmark which should trigger an Sync update immediately.

Regards
OnTheRocks

[therube]

Does the same happen with a FF trunk build?
Does it persist with the latest development build?


(I don't Sync.)

[OnTheRocks]

Does the same happen with a FF trunk build?
Does it persist with the latest development build?

I don't have set up an environment with Firefox and Sync. Testing was done with NoScript dev 2.4.2 rc4 and rc6.
Today I did another check. Syncing with SeaMonkey and NoScript still works with NoScript 2.4. But does not work with NoScript 2.4.1 and further on.

Regards
OnTheRocks

[OnTheRocks]

Syncing with SeaMonkey and NoScript still works with NoScript 2.4. But does not work with NoScript 2.4.1 and further on.

Strange. After going back once again to 2.4 the error is still there.
It seems that I can force Sync to work after checking the Sync quota via preference pane. So it could be that viewing quota does trigger the log in to Sync in another way than with standard Sync process and that the log in persist for some time.

Regards
OnTheRocks

[therube]

Does the issue persist if you start with a new, clean, Profile, with just NoScript installed?


Considering frickin FF (Mozilla) removed the build date from the UA, just what build are you using (though I'll assume you're as current as can be, which is actually a bit old ATM - for SeaMonkey).

(Ah, I see, they've now put up a build of the 18th.)

[OnTheRocks]

Does the issue persist if you start with a new, clean, Profile, with just NoScript installed?

Sorry for replying so late. But this turns out to be a bug in SeaMonkey itself:
http://bugzilla.mozilla.org/show_bug.cgi?id=758530
Don't know why this seemed to be working after disabling NoScript.

Regards
OnTheRocks