kialo not working unless "Disable restrictions globally" is set

[aron1616]

We use a popular debating and argument mapping site in our school, www.kialo.com and www.kialo-edu.com.

I wanted to tell students to install NS but ran into problems.

When logged in in kialo and others create changes, these appear in a discussion changes list (https://imgur.com/a/VECrGPk). These changes are acknowledged when seen. I guess these seen changes are sent to the server. When you reload, they don't appear anymore, as you have seen them already.

When using NS on FF this doesn't work, even when kialo.com is set to trusted. When "Disable restrictions globally" is enabled it works.

So either I am missing a domain to whitelist, but I don't see any, or something else is not working.

Please help!

In order to reproduce, create two kialo.com accounts, create a private debate, invite both users to the debate, create some arguments, see the changes for the other user, acknowledge them, reload and voila they reappear.

Thank you for any help!

Aron

[therube]

What version of NoScript?

There was a Chrome/NoScript/reload issue that the nightly version of NoScript may fix, viewtopic.php?p=101441#p101441.

[aron1616]

The most recent one, 11.0.10 from Dec 23 and it happens using FF.

I don't think it's a recent regression.

[Giorgio Maone]

I think I've found the culprit: Kialo uses a beacon request to update the "read" status of messages.
Please check latest dev version, thanks:

v 11.0.11rc1
============================================================
x Updated TLDs
x Added "ping" (beacon/ping) capability control

[aron1616]

Giorgio that indeed does the trick. Thank you!

I guess this is going to make it into the next release?

Keep up the great work!

[barbaz]

Please check latest dev version, thanks:

v 11.0.11rc1
============================================================
x Updated TLDs
x Added "ping" (beacon/ping) capability control

Something weird about how this got pushed to Github - the tag for 11.0.11rc1 is there, yet commit history is only up to 11.0.10.

[Giorgio Maone]

the tag for 11.0.11rc1 is there, yet commit history is only up to 11.0.10.

Fixed, thanks.