InformAction Forums

Hi I just had problems logging in to digg with the most obvious javascript domains whitelisted.

I didn't get the javascript alert() window telling me to login and when clicking the login link the css overlay box didnt appear until I lifted all permissions temporarily.

Just thought I'd tell you - you have been doing a great job in getting all these protections to work. I especially feel much safer with ABE on.

I tested using the latest development version, 1.9.7.3, and the transparent dialog appeared when I temp allowed just digg.com and facebook.com.
That kind of gossip/web networking site has so many domains playing on the page that the only way to find the culprit is by elimination.
For interest, the login page comes up fine without allowing any scripting at all. With this kind of fancy content problem, sometimes blocking all scripting can let a user access the workings of this kind of stuff.