Page 1 of 1

potential clickjacking at lawa traffic map

Posted: Fri Oct 13, 2017 6:52 pm
by davexnet
hello -
I'm trying to view the traffic map at this address:
http://www.lawa.org/laxtrafficmaps.aspx

This is the Los Angeles world airport site and their real-time traffic conditions.
Sometimes when I attempt to click and drag this map and/or zoom/unzoom, I get this error.

Why is it doing this and how can I set it so that it doesn't bother me anymore on this page?
Any info appreciated.

Image

Re: potential clickjacking at lawa traffic map

Posted: Fri Oct 13, 2017 7:19 pm
by barbaz
Please click the "Report" button on that ClearClick warning and post here the report ID. Then Giorgio can look into this when he gets the chance.

Re: potential clickjacking at lawa traffic map

Posted: Fri Oct 13, 2017 7:36 pm
by davexnet
barbaz wrote:Please click the "Report" button on that ClearClick warning and post here the report ID. Then Giorgio can look into this when he gets the chance.
I got report 913210 when attempting to use the zoom / unzoom buttons. Thanks for looking at this

Re: potential clickjacking at lawa traffic map

Posted: Sat Oct 14, 2017 10:58 pm
by barbaz
Since Giorgio is busy with other things atm, I decided to check this myself while we wait.

I can reproduce the ClearClick warning. I do not believe actual clickjacking is involved here, so to work around the problem -

about:config > noscript.clearClick.exceptions
add on the end, separated by a single space -

Code: Select all

www.lawa.org
This disables ClearClick on that domain.

Re: potential clickjacking at lawa traffic map

Posted: Sun Oct 15, 2017 2:42 am
by davexnet
barbaz wrote:Since Giorgio is busy with other things atm, I decided to check this myself while we wait.

I can reproduce the ClearClick warning. I do not believe actual clickjacking is involved here, so to work around the problem -

about:config > noscript.clearClick.exceptions
add on the end, separated by a single space -

Code: Select all

www.lawa.org
This disables ClearClick on that domain.
Thanks for this - have added this workaround
Dave