The iframe is set as noborder so it appears completely seamless to the end user. So we have the applications set up to run on one website and then embedded these into our other websites using an iframe, enabling simple javascript parameter passing so we can integrate the selection of a tartan or clan with functionality on the embedding site. The database behind this is surprisingly large (nearly ten thousand rows in the core names and tartans tables) and fairly regularly updated. As part of this we have developed a couple of simple applications to locate possible clan names from your surname or your choice of tartans (giggle if you wish but tartans are worth $700 million a year to our economy). Basically you can use JQuery to call the content based on which nav item the user clicks and then load it in the content container. While both frames and iframes perform a similar function embedding a resource into a webpage they are fundamentally different. In particular embedding common functionality across multiple sites.įor example I have a client who runs a number of Scottish goods e-commerce sites. Andy Howells Participant Okay, your best bet then is AJAX. An iframe, on the other hand, embeds a frame directly inline with the other elements of a webpage.
They can be extremely useful in some circumstances, but those are limited. But if you need to interact with the contents of the IFrame in certain ways, then IFrame may be necessary. So, it seems like if you're just using IFrame to display something, there's other tags like Object that can be used instead. Object does not have a contentWindow property, so there's no way to print only the section of the page. IFrame has a contentWindow property, that's what makes printing only that part possible.
Tip: Use CSS to style the