iFrame loading errors

Hi,
I am having a problem when I load multiple iFrame channels on the same layout. The two issues I have found are as follows:

  1. If I change the iFrame height in the channel definition, the channel will sporadically concatenate the old height with the new height, which results in a channel that is over 400000px. Example: I had a frame that was originally defined as 400px, but it was getting cut off, so Lum added scroll bars - I decided to change the height to 450px to allow the content to display properly. When I loaded the page, the channel was 400450px! (I used Firebug to inspect the element, that is how I know the height) - I am guessing it has something to do with the cache, but this still happens days after I have editing the height.
  2. When pulling the URL for the iFrame, Lum is again concatenating the URLS of two iFrames, which results in a "Page cannot be displayed". I did notice that the concatenation is the URL of the iFrame + the URL of the iFrame that is positioned in the channel above the one affect. 

Anyone have this issue?
 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

iframe Very Tall - Height Concatenation

Yes, I've verified that I have the same issue.  Some times when you view the iframes they're fine.  Other times they have the previous and current heights concatenated together.  I'm looking at one right now where:

iFrame problem with Framed Tab

We currently have a set of tabs that wrap. While trying to fix the javascript for calculating the height of the IFrame (for framed tabs), we have encountered a different problem.

(Other than the hard coded height of the top section (banner+icons+tabs) being 400 pixels)

When Firefox is refreshed, the javascript returns a different value for the height.

This means that instead of having a beautifully calculated height, with no scroll bars unless they are needed. We get a very small IFrame with lots of scroll bars.

Derek

University of Leeds, UK

We see this also

Has anyone found a fix for this issue?

Syndicate content