[gwt-contrib] Re: Warning message in IE6 when using NamedFrame on SSL-secured web-site

2008-12-10 Thread David
Using javascript:'' for any IFRAME should be done as a default, without even thinking about the possible use. There were bugs in the past in FormPanel and PopupPanel in IE6 for the exact same reason. David On Tue, Dec 9, 2008 at 9:34 PM, Emily Crutcher [EMAIL PROTECTED] wrote: Why is this a

[gwt-contrib] Re: Warning message in IE6 when using NamedFrame on SSL-secured web-site

2008-12-09 Thread jlabanca
The diff didn't go through for DefaultMuseum.java. Here is that part of the patch: Index: reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java === ---

[gwt-contrib] Re: Warning message in IE6 when using NamedFrame on SSL-secured web-site

2008-12-09 Thread John LaBanca
Frames are used to load external sites, so the src is likely an actual URL, whereas NamedFrames are used locally and in FormPanels. While NamedFrames can be used for external sites and vice versa, that isn't the default use case. Also, people can change the URL of a NamedFrame via setUrl(), and

[gwt-contrib] Re: Warning message in IE6 when using NamedFrame on SSL-secured web-site

2008-12-09 Thread Emily Crutcher
Why is this a problem for NamedFrames but not Frames? Other then that, LGTM. On Tue, Dec 9, 2008 at 3:10 PM, [EMAIL PROTECTED] wrote: Reviewers: ecc, Description: Description: The iframe created in a NamedFrame does not have a src, so it throws a mixed content warning in IE6