Dan Ehrmann
Top achievements
Rank 1
Rank 1
Dan Ehrmann
asked on 30 May 2009, 12:55 AM
On my site, users will sometimes insert images or iframes from different sites into their pages. To avoid getting the mixed content warnings, we modify urls in 'src' attributes to use https when need the rest of the page is also using https. This is fine, except when the other sites do not serve content using https. For these cases, we instruct users to add a prefix to the 'src' url so that we do not modify it. So, an iframe might look like this:
<iframe src='nossl-http://someothersite.com/page.html' />
Before displaying the page, we remove the 'nossl-' but do not convert 'http' to 'https'.
For one of our customers, opening content in the editor including only an iframe similar to the example above causes a hard Firefox crash. I have tried the exact same iframe tag on other sites (running on the same platform, same browser, same client computer) and there is no problem (Firefox displays an error message about the weird protocol, but that is expected).
So, I am wondering if you have any ideas on what could cause this. I can't create a sample project, because it only happens for the one customer.
<iframe src='nossl-http://someothersite.com/page.html' />
Before displaying the page, we remove the 'nossl-' but do not convert 'http' to 'https'.
For one of our customers, opening content in the editor including only an iframe similar to the example above causes a hard Firefox crash. I have tried the exact same iframe tag on other sites (running on the same platform, same browser, same client computer) and there is no problem (Firefox displays an error message about the weird protocol, but that is expected).
So, I am wondering if you have any ideas on what could cause this. I can't create a sample project, because it only happens for the one customer.
5 Answers, 1 is accepted
0
Hi Dan,
Your scenario (and approach thereof) is fairly specific, and you are the first to report such a problem. We are not sure what could be causing the problem (as you point out yourself, it only happens on a single machine).
Some suggestions for you to explore further are:
1. Try the same HTML content (with the IFRAME) on the page - but do not add it into the editor's content area - just output it on the page itself and see how the browser behaves.
2. Compare the installed FireFox plugins in the problematic browser, as well as the correctly working browser(s).
3. Uninstall FireFox from the problematic machine and install it again (this will hint whether the problem was in the actual browser installation).
Best regards,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Your scenario (and approach thereof) is fairly specific, and you are the first to report such a problem. We are not sure what could be causing the problem (as you point out yourself, it only happens on a single machine).
Some suggestions for you to explore further are:
1. Try the same HTML content (with the IFRAME) on the page - but do not add it into the editor's content area - just output it on the page itself and see how the browser behaves.
2. Compare the installed FireFox plugins in the problematic browser, as well as the correctly working browser(s).
3. Uninstall FireFox from the problematic machine and install it again (this will hint whether the problem was in the actual browser installation).
Best regards,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Dan Ehrmann
Top achievements
Rank 1
Rank 1
answered on 01 Jun 2009, 04:47 PM
Thanx Tervel -
This has actually happened on two different computers, both running Firefox 3.0.10 - on mine it is intermittent - sometimes it works and sometimes it crashes. I have the usual assortment of plug-ins for developers (firebug, etc). Everything is up to date. I am waiting for detailed plug-in info from my customer.
On another computer in the office running Firefox 3.0.1 (with no plug-ins), we have been unable to reproduce the problem.
The iframe content displays correctly on other pages. It is very simple html - no script or anything but a short list of links.
I don't think this is a Telerik problem - I was just wondering if you had seen anything like it before.
Firefox offers to send crash details to Mozilla, which I have done - maybe they will come up with something...
I will open a support ticket so I can send you the iframe content in question and a url with login info where you can try it yourself
0
Hello Dan,
Yes, if/once you gather additional information about the issue, please share it with us - hopefully eventually we will be able to reproduce the problem and find out the reason for it.
On a side note, it seems that I was not 100% clear on one of my suggestions. When I said "Try the same HTML content (with the IFRAME) on the page...", I meant the following:
1. You mention that the original problem comes from having an iframe declaration with a src referring to a non-existing protocol, which has been inserted into the editor's content area.
2. My suggestion was to test this very same iframe declaration on the page (without RadEditor).
When you write "The iframe content displays correctly on other pages.", I am not sure whether you followed the exact suggestion - because, to my understanding, since the protocol is non-existent, nothing should load in the iframe. Could it be that instead you actually changed the <iframe> src to be correct? Essentially, my point here is - please test the same problematic content (as it is into the editor) outside of the editor and see whether the same behavior occurs.
Best regards,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Yes, if/once you gather additional information about the issue, please share it with us - hopefully eventually we will be able to reproduce the problem and find out the reason for it.
On a side note, it seems that I was not 100% clear on one of my suggestions. When I said "Try the same HTML content (with the IFRAME) on the page...", I meant the following:
1. You mention that the original problem comes from having an iframe declaration with a src referring to a non-existing protocol, which has been inserted into the editor's content area.
2. My suggestion was to test this very same iframe declaration on the page (without RadEditor).
When you write "The iframe content displays correctly on other pages.", I am not sure whether you followed the exact suggestion - because, to my understanding, since the protocol is non-existent, nothing should load in the iframe. Could it be that instead you actually changed the <iframe> src to be correct? Essentially, my point here is - please test the same problematic content (as it is into the editor) outside of the editor and see whether the same behavior occurs.
Best regards,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Dan Ehrmann
Top achievements
Rank 1
Rank 1
answered on 02 Jun 2009, 12:06 PM
Your suggestion was clear - I just didn't read it clearly :)
I put the iframe with the mangled 'src' on an otherwise blank page and it did not crash Firefox like it does in the editor. However, since this problem is intermittent, I might just have gotten lucky.
I put the iframe with the mangled 'src' on an otherwise blank page and it did not crash Firefox like it does in the editor. However, since this problem is intermittent, I might just have gotten lucky.
0
Dan Ehrmann
Top achievements
Rank 1
Rank 1
answered on 02 Jun 2009, 02:05 PM
Another experiment - I tried this in the editor demo at Mozilla (http://www.mozilla.org/editor/midasdemo/) and it did not crash. Again, since it is an intermittent problem, this may not mean anything significant.