InformAction Forums

5.1.7: Not sure if ClearClick is working?

SeaMonkey 2.49.2 x64

I'm see a background tab "play" (you post, & the page refreshes when seemingly it shouldn't be - yet).

Pretty sure I named the correct feature, ClearClick.

Nope .

Background tab should not refresh (like when posting in a forum) until the tab [again] gains focus, right.

Yep, does seem to be broken.

XP, SeaMonkey 2.49.1, NoScript 5.1.7.

FF 52 does look to be working as expected.

[NoScript] Blocking refresh on unfocused tab, https://forums.informaction.com/posting ... 22&t=23716

Oh, & that's weird.
It also just now worked - in the same SeaMonkey Profile where a moment ago it did not work.

[NoScript] Blocking refresh on unfocused tab, https://forums.informaction.com/posting ... 22&t=23717

And at the same time, it is NOT working at http://forums.mozillazine.org/index.php.
Post & immediately jump to a new tab.
Notice (without actually return to the tab, yet) that the background tab does "refresh".
Nothing noted in Error Console that anything was blocked.
Now return to that tab, & note that it had indeed refreshed.


Most likely I did notice that at mozillazine, & had only test there.

For FF & XP, I thought, oh, I can just test here, informaction.

So I guess I now need to test FF at mozillazine...


FF 52 does seem to be working - at mozillazine.
So this might be SeaMonkey specific.

[NoScript] Blocking refresh on unfocused tab, http://forums.mozillazine.org/posting.p ... #p14779197

And in another test, new, clean SeaMonkey Profile, install 5.1.7, restart & post: So Error Console did log the "block", but in fact the action, refresh, was not blocked.

And yet in further, same Profile, go back, Edit, Submit, it was blocked as expected?

So... ?

therube wrote:Pretty sure I named the correct feature, ClearClick.
Background tab should not refresh (like when posting in a forum) until the tab [again] gains focus, right.

That feature is not ClearClick. It's NoScript's tabnapping protection, controlled by about:config > noscript.forbidBGRefresh* prefs.

(OK, I'll change the Subject.)

So... ?

Maybe its a timing issue?
Obviously being too slow to jump away will allow the refresh.
But is being too fast in jumping away also allowing it?