That's a great fix, thanks! Peter
On 1/19/07, Jonathan Sharp <[EMAIL PROTECTED]> wrote:
Take a look at my plugin: http://jdsharp.us/code/jQuery/jdMenu/ The work around is to append '</iframe>' first and then the open iframe. Look at the example in my code. We encountered the same issue with the security warning. I believe this is also the solution that sourceforge implemented for their menus. This solution could be factored into the bgiframe plugin. -js On 1/19/07, Peter Vulgaris <[EMAIL PROTECTED]> wrote: > Whenever I tried using Autocomplete over https with IE 6, I would get a > security message upon first entering a query. This was caused by the iframe > being created in the background, or more specifically the fact that the > iframe had no src set. The only solution I've found to work is creating a > blank file and pointing the src to it like this: > > // we put a styled iframe behind the calendar so HTML SELECT elements > don't show through > //$results.append(document.createElement('iframe')); // original code > $results.append($( > '<iframe src="' + window.location.protocol + '//' + > window.location.hostname + > window.location.pathname + 'blank.html"></iframe>' > )); // new code > > I could've just left out the blank.html but then I'd be doubling the > amount of data the client needs to transfer (once for the page itself and > once for the same page in the iframe). Has anyone come across this and found > a better solution? > > Peter > > _______________________________________________ > jQuery mailing list > discuss@jquery.com > http://jquery.com/discuss/ > > > _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
_______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
