tedster
msg:3922071 | 11:02 pm on May 28, 2009 (gmt 0) |
Yes, it is most always code on the other page that makes it break out of your frameset. Framebrreaker (framebuster) code is common on sites who do not want to show up inside someone else's frame.
|
iamvela
msg:3922231 | 6:43 am on May 29, 2009 (gmt 0) |
Right, I understand that but is there a way to make sure that, that is what is happening here?
|
bill
msg:3922265 | 8:04 am on May 29, 2009 (gmt 0) |
Look at the source of the site in question. That sort of script may be in the <head>.
|
iamvela
msg:3922267 | 8:16 am on May 29, 2009 (gmt 0) |
Yeah, we already looked and dont see it at all! Even looked inside externally referenced javascripts.
|
tangor
msg:3922783 | 2:27 am on May 30, 2009 (gmt 0) |
Isn't there an issue with inserting an HTTPS page (secured) inside an HTTP (unsecured) page? Seem to recall the two frames will no longer communicate with each other. But then again, it's been a LONG time since I looked into frameset!
|
|
