Meebo pop-out window blocked (while in whitelist)

[John/CP44]

Meebo has a pop-out Window that seems to have stopped working in recent versions of NoScript.
Disabling the NoScript add-on seems to allow the pop-out window to work properly.
Both meebo.com and meebocdn.net are in my NoScript whitelist.

The URL of the pop-out window becomes http://www.meebo.com/popup.html#
When the pop-up opens properly, AdBlock says all identifiable items are from s.meebocdn.net (which would seem to be allowed by whitelist); and I can't identify anything more that would be problematic.

--John/CP44

[Giorgio Maone]

Could you get latest development build and check whether the problem persist?
If it does, is it go away if you set the noscript.surrogate.enabled about:config preference to false?

[John/CP44]

Using what you gave me, here's my step list:
Installed development release "2.0.3rc2" from http://noscript.net/getit#devel
No change to the problem: clicking the pop-out button causes the pop-up to flash and disappear; all future pop-out button clicks have no effect.

Going to about:config and finding "noscript.surrogate.enabled" was easy enough, double-clicking set it to false...
...couldn't find a way to commit the change so I closed the tab and restarted FireFox - "noscript.surrogate.enabled" was then "true" on restart.
If there's a special save command for the about:config page, I must not know about it - but I assumed the value was getting reset or read from somewhere else on load.
Searched around a bit, found %UserProfile%\Application Data\Mozilla\Firefox\Profiles\218p8kjm.default\extensions\{73a6fe31-595d-460b-a920-fcc0f8843232}\defaults\preferences\noscript.js with a "noscript.surrogate.enabled" entry... I set that to "false" and saved the file while FireFox was shut down.

Next time FireFox opened, I verified about:config showed "noscript.surrogate.enabled"="false" and then went to meebo.
The pop-outs now work properly again.

My notes:
The change of "noscript.surrogate.enabled" to "false" from about:config was not saved on program exit.
The surrogate function could/should be the issue (last change before success). Anything you can tell me about it?

I hope I've been a helpful user
Many thanks for your help, Mr. Maone!