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.
There is a solution called “Fragment Id Messaging” to solve cross domain communication by setting parent.location with extra texts followed by “#” from child iframe, it works. However, if the parent itself is embedded as an iframe in another page, parent.location setting seems denied by browsers…
Is this true? If yes, is there a work-around?
Thanks!
Which browsers are you encountering a problem, and what’s the exact error message you see?
Generally, FIM should work correctly even in the scenario you describe, and many major websites use it.
FIM should only be used when the HTML5 postMessage API (supported by IE8, FF3, Chrome, and Opera 10) is not available, as postMessage is more secure and more reliable.