Thanks for the replies John & Jens,
The app can run in http/https, the user can then configure the app to
consume various resources, for example rss feeds, web services - in
this instance the feed resources contained images which were then
loaded over http.
The issue was/is that IE throws a javas
Comment by khi...@googlemail.com:
someone's using netbeans ?
For more information:
http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Revision: 10660
Author: pengzhu...@google.com
Date: Tue Sep 20 07:04:28 2011
Log: During row mouseout events, only consider it as row unhovering if
the
event coordinates are outside the hovering row. Previously, if there's a
popup
dialog floating on top of a table row, moving into t
Revision: 10659
Author: y...@google.com
Date: Tue Sep 20 06:09:15 2011
Log: Fix javadoc for new timezone-aware constructors of DateCell.
Review at http://gwt-code-reviews.appspot.com/1545803
Review by: jlaba...@google.com
http://code.google.com/p/google-web-toolkit/source/detail?r=106
Revision: 10658
Author: gwt.mirror...@gmail.com
Date: Tue Sep 20 05:39:26 2011
Log: Allow DateBox to fire events with null date values for invalid
and empty input
strings.
Review at http://gwt-code-reviews.appspot.com/1552803
http://code.google.com/p/google-web-toolkit/source/detai
I think its a mixed-mode content problem (HTTPS for app and HTTP for your
requested image). I can't see the issue in our app which uses HTTPS for both
the app and all resources (to avoid the mixed-mode warning of browsers).
-- J.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributor
On Tue, Sep 20, 2011 at 4:20 AM, DaveC wrote:
> There was also another runtime Exception being thrown - this time the
> culprit was the iFrame for GWT History (the exception was thrown at
> the point the iframe's document was being accessed)... it was unused
> and removing it fixed the problem.
>
There was also another runtime Exception being thrown - this time the
culprit was the iFrame for GWT History (the exception was thrown at
the point the iframe's document was being accessed)... it was unused
and removing it fixed the problem.
I find it hard to believe that no one else has seen this
