Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I mean accessing it from .NET code, not javascript. Is this just a negative vestige from javascript’s security restrictions or is this something that is there for a real reason? I frankly can’t find any.
I mean you can probably erase the guy’s hard drive from code, but you can’t access the contents of an iFrame…
I am pretty sure this limitation is connected to Internet Explorer’s XSS (Cross Site Scripting) security. I suggest briefly turning off XSS protection in IE’s security settings and having another go. If I remember correctly, the security settings for the winform browser are taken from the default version of IE, so changes in IE security apply to your form. In IE 8 you can turn off XSS protection through “Internet Options->Security->Custom Level” and checking the disable radio button for “Enable XSS Filter”.