Always “hover” before you click? Wrong.

Re:Always “hover” before you click? Wrong. by madsr on Monday October 29, 2012 @10:25AM (#4712381)

And this is why we use Firefox with NoScript on unknown sites :-)

[ Parent | on HN ]

Re:Always “hover” before you click? Wrong. by mike-cardwell on Tuesday October 30, 2012 @06:12AM (#4716786)

RequestPolicy also protects against this by asking the user for confirmation before visiting any new domain unless the request was initiated by the user. In this case, RequestPolicy would detect that the request for a URL on a new domain was generated by JavaScript.

So even if you enable JavaScript on a site, RequestPolicy is a good second line of defence.

[ Parent | on HN ]

Re:Always “hover” before you click? Wrong. by ygra on Monday October 29, 2012 @10:42AM (#4712461)

I wouldn't count Google as unknown ;-)

[ Parent | on HN ]

Re:Always “hover” before you click? Wrong. by madsr on Monday October 29, 2012 @10:53AM (#4712512)

Google isn't, but the page providing the link (frameloss.org) is unknown (to me).

[ Parent | on HN ]