InformAction Forums

Hi,

I am having a problem with ClearClick interfering with the FloatNotes Firefox extension. I have white listed floatnotes: and the site I am using FloatNotes on and I have also unchecked the NoScript option "ClearClick protection on pages... trusted". However, when I click inside a FloatNote I get 3 messages in the Error Console of the following form:
This prevents minimized FloatNotes from being expanded again.

I am using NoScript 2.3.6

Does anybody have a suggestion?

Thanks

Do you get an actual ClearClick warning box popping up on the screen? If so, please click "Send report", so that a report will be sent to Giorgio for analysis.
(Private information will be kept confidential, of course.)

Then note the Report ID# (six digits, I think), and post it here, so that the analysis and remedy can be posted here, thanks.

Hi TomT,

I am afraid I don't get an actual ClearClick warning box, just the 3 messages written to the Error Console

Link: FloatNotes

therube wrote:Link: FloatNotes

Did you have an actual solution there, or is the link just so I could download and install FloatNotes?

I could probably find the add-on myself. Anything specific on that link *that actually addresses the issue"?


@ endofmiles:

I think we have the answer: Install latest development build

v 2.3.7rc3
x [ClearClick] Work-around for "rapid fire" protection interfering with some add-ons, ssuch as 1Password (thanks Mike Tselikman for report)

Your reports too cite "rapid fire" protection, so please install this version and let us know if it fixes the issue for you.

Hi TomT

I installed NoScript 2.3.7rc3 but it has not helped with this problem.

Here are the exact 3 messages to the error console:

Guest wrote:Hi TomT

I installed NoScript 2.3.7rc3 but it has not helped with this problem.

Here are the exact 3 messages to the error console:

Code: Select all

[NoScript ClearClick] Swallowed event mousedown on http://www.google.com/ (rapid fire from floatnotes: in 400ms)

Code: Select all

[NoScript ClearClick] Swallowed event mouseup on http://www.google.com/ (rapid fire from floatnotes: in 400ms)

Code: Select all

[NoScript ClearClick] Swallowed event click on http://www.google.com/ (rapid fire from floatnotes: in 400ms)

Thanks, those are very helpful.

I'm sorry that the development build didn't fix your specific "rapid fire" issue, so I'll call this to Giorgio's attention.
Probably just another slight tweak to the "rapid fire" protection. Thanks for the report.

Please check latest development build 2.3.7rc4, thanks.

Hi Giorgio,

NoScript 2.3.7rc4 still prevents a minimized FloatNote from being expanded but this time only produces two messages in the error console
and Thank you for looking into this.

endofmiles wrote:Hi Giorgio,

NoScript 2.3.7rc4 still prevents a minimized FloatNote from being expanded but this time only produces two messages in the error console

Code: Select all

[NoScript ClearClick] Swallowed event mouseup on floatnotes:blank (rapid fire from http://www.google.com in 400ms)

and

Code: Select all

[NoScript ClearClick] Swallowed event click on floatnotes:blank (rapid fire from http://www.google.com in 400ms)

Thank you for looking into this.

One down, two to go.

At least we got rid of the mousedown error. I'll give Giorgio a heads-up that there's still another tweak or two needed, thanks.

Please check latest development build 2.3.7rc5, thanks.

Thank you very much Giorgio,
2.3.7rc5 fixed the issue completely.

endofmiles wrote:Thank you very much Giorgio,
2.3.7rc5 fixed the issue completely.

YESSSS!!!!

Thanks, Giorgio. Will mark as resolved.

Does endofmiles not get Changelog credit for reporting due to being unregistered? The guest username was consistent... not sure of the policy about that.

Tom T. wrote: Does endofmiles not get Changelog credit for reporting due to being unregistered? The guest username was consistent... not sure of the policy about that.

It did get credit in the stable version condensed changelog.

Giorgio Maone wrote:

Tom T. wrote: Does endofmiles not get Changelog credit for reporting due to being unregistered? The guest username was consistent... not sure of the policy about that.

It did get credit in the stable version condensed changelog.

IDK that 2.3.7 had become stable, thanks.
And I wasn't hinting, but ... thanks anyway.