Make sure you modify the following native method to point to your own
package structure:
public native void setMyOnload(JavaScriptObject elm, MyNamedFrame
frame)/*-{
elm.myonload = function(event){
fra...@com.skystrider.subtabs.client.gwtutils.mynamedframe::onload(Lcom/
As it turns out, IE does NOT support programmatically setting the
onload attribute of the iframe. The solution is to set the onload
attribute in the html tab to call another function, which is the
function you programmatically set.
My following post will include all the code for the new solution,
package com.skystrider.subtabs.client.gwtUtils;
import java.util.ArrayList;
import com.google.gwt.core.client.GWT;
import com.google.gwt.core.client.JavaScriptObject;
import com.google.gwt.dom.client.IFrameElement;
import com.google.gwt.user.client.DOM;
import com.google.gwt.user.client.Element;
hi sky!
that looks pretty much like our implementation...;)
this is the problem of such a big toolkit like GWT, there are too many
'features' (like widgets, rpc, jre emulation, java-to-js compilation,
the new data driven widgets and so on) which is great for a fast start
and even enough for many
Just in case you ever wanted to have a handler for the iframe's
onload event:
import com.google.gwt.event.dom.client.HasLoadHandlers;
import com.google.gwt.event.dom.client.LoadEvent;
import com.google.gwt.event.dom.client.LoadHandler;
import com.google.gwt.event.shared.HandlerRegistration;
