gwtproject / gwt

GWT Open Source Project

GWT

GWT is the official open source project for GWT releases 2.5 and onwards.

In this document you have some quick instructions to build the SDK from source code and to run its tests.

For a more detailed documentation visit our web site. If you are interested in contributing with the project, please read the Making GWT better section.

Building the GWT SDK:

• In order to build GWT, java and ant are required in your system.

• You need the GWT tools repository checked out and up-to-date. By default it is expected to be found at ../tools. You can override the default location using the GWT_TOOLS environment variable or passing -Dgwt.tools= argument to ant.

• To create the SDK distribution files run:

  $ ant clean dist-dev

  Then you will get all .jar files in the folder build/lib and the redistributable file will be: build/dist/gwt-0.0.0.zip

  if you want to specify a different version number run:

  $ ant clean dist-dev -Dgwt.version=x.x.x

• To compile everything including examples you have to run

  $ ant clean dist

• To create maven artifacts (after building .jar using ant), use following guide.

How to verify GWT code conventions:

• In GWT we have some conventions so as all code written by contributors look similar being easier to review.

• After you make any modification, run this command to compile everything including tests, to check APIs, and to verify code style. It shouldn't take longer than 3-4 minutes.

  $ ant compile.tests apicheck checkstyle

How to run GWT tests

• Previously to run any test you have to set some environment variables to guarantee that they are run in the same conditions for all developers.

  In a Unix like platform you can use the export command:

  $ export TZ=America/Los_Angeles ANT_OPTS=-Dfile.encoding=UTF-8

  But in Windows™ you have to set the time-zone in your control panel, and the environment variables using the command set.

• Finally you can run all test suites with the following command, but be prepared because it could take hours, and probably it would fail because of timeouts, etc.

  $ ant test

• Thus, you might want to run only certain tests so as you can focus on checking the modifications you are working on.

  GWT build scripts use specific ant tasks and a bunch of system properties listed in the following table to specify which tests to run and how.

  For instance to run the task test in the module user you have to change to the user folder and run ant with the task as argument, adding any other property with the -D flag:

  $ ( cd user && ant test -Dtest.emma.htmlunit.disable=true ; cd .. )

  Module	Task	Property to skip	Description
  dev	test	test.dev.disable	GWT compiler & dev libraries
  codeserver	test	test.codeserver.disable	SuperDevMode server
  user	test	test.user.disable	GWT user API and JRE emulation
  user	test.nongwt	test.nongwt.disable	Run tests that not require GWTTestCase
  user	test.dev.htmlunit	test.dev.htmlunit.disable	Run dev-mode tests with HtmlUnit
  user	test.web.htmlunit	test.web.htmlunit.disable	Run web-mode tests with HtmlUnit
  user	test.draft.htmlunit	test.draft.htmlunit.disable	Run draft compiled HtmlUnit tests
  user	test.nometa.htmlunit	test.nometa.htmlunit.disable	Run -XdisableClassMetadata tests with HtmlUnit
  user	test.emma.htmlunit	test.emma.htmlunit.disable	Run emma tests with HtmlUnit
  user	test.coverage.htmlunit	test.coverage.htmlunit.disable	Run tests for coverage support
  user	test.dev.selenium	test.dev.selenium.disable	Run dev-mode tests using Selenium RC servers
  user	test.web.selenium	test.web.selenium.disable	Run web tests using Selenium RC servers
  user	test.draft.selenium	test.draft.selenium.disable	Run draft compiled tests using Selenium RC servers
  user	test.nometa.selenium	test.nometa.selenium.disable	Run -XdisableClassMetadata tests using Selenium RC servers
  user	test.emma.selenium	test.emma.selenium.disable	Run emma tests with Selenium RC servers
  requestfactory	test	test.requestfactory.disable	Request Factory library
  tools	test	test.tools.disable	Some tools used in GWT development

  Additionally you can utilize some variables to filter which test to run in each task:

  Module	Task	Properties	Default
  dev/core	test	gwt.junit.testcase.dev.core.includes	**/com/google/**/*Test.class
  		gwt.junit.testcase.dev.core.excludes
  user	test	gwt.junit.testcase.includes	**/*Suite.class
  user	test.nongwt	gwt.nongwt.testcase.includes	**/*JreSuite.class
  		gwt.nongwt.testcase.excludes
  user	test.web.* test.draft.* test.nometa.*	gwt.junit.testcase.web.includes	**/*Suite.class
  		gwt.junit.testcase.web.excludes	**/*JsInteropSuite.class,**/*JreSuite.class,***/OptimizedOnly*
  user	test.dev.* test.emma.*	gwt.junit.testcase.dev.includes	**/*Suite.class
  		gwt.junit.testcase.dev.excludes	**/*JsInteropSuite.class,**/*JreSuite.class,***/OptimizedOnly*

Examples

• Run all tests in dev

  $ ( cd dev && ant test ; cd .. )

  Note: that the last `cd ..' is only needed in Windows.

• There is another option to do the same but without changing to the module folder. We have to specify the module as the ant task, and the task as a target argument.

  $ ant dev -Dtarget=test

• Run all tests in codeserver

  $ ( cd dev/codeserver && ant test )

  or

  $ ant codeserver -Dtarget=test -Dtest.dev.disable=true

  Note: that we disable dev tests because code server depends on dev and we don`t want to run its tests.

• Run all tests in tools

  $ ant tools -Dtarget=test -Dtest.dev.disable=true -Dtest.user.disable=true

• Run only the JsniRefTest in dev

  $ ant dev -Dtarget=test \
      -Dgwt.junit.testcase.dev.core.includes="**/JsniRefTest.class"
  

• Run a couple of tests in dev

  $ ant dev -Dtarget=test \
      -Dgwt.junit.testcase.dev.core.includes="**/JsniRefTest.class,**/JsParserTest.class"
  

  Note: that you have to use regular expressions separated by comma to select the test classes to execute.

• Run all Jre tests in user, they should take not longer than 3min. We have two ways to run them. Although the second case is more complex it is here to know how disable properties work.

  $ ( cd user && ant test.nongwt )

  or

  $ ant user -Dtarget=test
         -Dtest.dev.disable=true \
         -Dtest.codeserver.disable=true \
         -Dtest.requestfactory.disable=true \
         -Dtest.tools.disable=true \
         -Dtest.dev.htmlunit.disable=true \
         -Dtest.web.htmlunit.disable=true \
         -Dtest.coverage.htmlunit.disable=true \
         -Dtest.dev.selenium.disable=true \
         -Dtest.draft.htmlunit.disable=true \
         -Dtest.draft.selenium.disable=true \
         -Dtest.emma.htmlunit.disable=true \
         -Dtest.emma.selenium.disable=true \
         -Dtest.nometa.htmlunit.disable=true \
         -Dtest.nometa.selenium.disable=true \
         -Dtest.web.selenium.disable=true
  

  Note: that we have to set all disable variables but test.nongwt.disable

• Run certain Jre tests in the user module.

  $ ( cd user && ant test.nongwt -Dgwt.nongwt.testcase.includes="**/I18NJreSuite.class" )

• Run all GWT tests in user using htmlunit in dev mode.

  $ ( cd user && ant test.dev.htmlunit )

gwt's Issues

Include a reset() method in FormPanel

Originally reported on Google Code with ID 32

GWT Release:
1.1.10

Browser or OS version (if applicable):

Detailed description:

It would be nice to have a way to reset a FormPanel.

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/1d1cd0b801afe284

Reported by gwt.team.vli on 2006-09-20 06:05:32

Change the text of ListBox item

Originally reported on Google Code with ID 33

GWT Release:
1.1.10
Browser or OS version (if applicable):

Detailed description:
There is no method to change the text of a an item once it has already been
added, such as listbox.setText(index, newtext);

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/b82b45ca782da65c

Reported by gwt.team.vli on 2006-09-20 06:21:54

DOM.toString() gives different results on Internet Explorer and Firefox.

Originally reported on Google Code with ID 1

GWT Release:
1.1.10

Browser or OS version (if applicable):
   mozilla, IE6

Detailed description:
DOM.toString() gives different results on Internet Explorer and Firefox.

Example code showing the problem (strongly preferred):
 Button b = new Button("Show Html", new ClickListener() {
     public void onClick(Widget sender) {
       Label l = new Label(DOM.toString(table.getElement()));
       p.add(l);
     }

   });
   p.add(b);
 }

Reported by gwt.team.hcc on 2006-09-15 18:23:37

FireFox bug w/Panels in grids? [Horizontal alignment or rowspan]

Originally reported on Google Code with ID 15

GWT Release:
1.10
Browser or OS version (if applicable):
FireFox
Detailed description:
Horizontal alignment does not work for FireFox as textAlign is treated
differently in IE and FireFox

Example code showing the problem (strongly preferred):
public void onModuleLoad() {
  FlexTable table = new FlexTable();
  table.setBorderWidth(1);

  HorizontalPanel hp = new HorizontalPanel();
  hp.add(new Button("OK"));
  hp.add(new Button("Cancel"));

  table.setWidget(0, 0, new Label("Long Value for Cell 0,0"));
  table.setWidget(0, 1, new Label("Long Value for Cell 0,1"));
  table.setWidget(1, 0, hp);

  table.getFlexCellFormatter().setColSpan(1, 0, 2);
  table.getFlexCellFormatter().setHorizontalAlignment(1, 0,
HasHorizontalAlignment.ALIGN_RIGHT);

  RootPanel.get().add(table);

}

Workaround if you have one:
Manually set the "align" attribute on the table cell.

Links to the relevant discussion group topics (optional):

Reported by gwt.team.ecc on 2006-09-18 12:12:31

ListBox does not fire focus and key events

Originally reported on Google Code with ID 14

GWT Release:
1.10
Browser or OS version (if applicable):
all
Detailed description:
ListBox is not firing focus and key events
Example code showing the problem (strongly preferred):
http://www.asquare.net/gwt/bugs/
Workaround if you have one:
The current implementation of ListBox is unable to dispatch any events
except onChange.

To capture a different event (like onClick), do the following:
1. Call sinkEvents(Event.ONCLICK) on the ListBox.
2. Override the listbox's onBrowser event like so:
  protected ListBox box = new ListBox() {
    public void onBrowserEvent(Event event) {
      if (Event.ONCLICK == DOM.eventGetType(event)) {
        // Do onClick handling here.
      }
    }
  };


Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/2fa972345c665b43
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/f8428d2d838fbc7e

Reported by gwt.team.ecc on 2006-09-18 12:07:12

setKeyCode doesn't work in firefox

Originally reported on Google Code with ID 25

GWT Release: 1.1.10

Browser or OS version (if applicable):
Firefox

Detailed description:
setKeyCode doesn't work in Firefox. In Firefox, event.keyCode is a read
only value. 

Example code showing the problem (strongly preferred):

Workaround if you have one:
In order to change a keycode, you need to cancel the current event, and
dispatch a new key event with the new keycode. 

public class FireFoxTextBox extends TextBox {
        public void onBrowserEvent(Event event) {
            int type = DOM.eventGetType(event);
            if (type == Event.ONKEYPRESS) {
                   changeKeyCode(event);
            } else
                super.onBrowserEvent(event);
        }

        public native void changeKeyCode(Event event) /*-{

           if (String.fromCharCode(event.charCode) == "Q") {
                  var newEvent = document.createEvent("KeyEvents")
                  newEvent.initKeyEvent("keypress", true, true,
document.defaultView,
                  event.ctrlKey, event.altKey, event.shiftKey,
                  event.metaKey, 0, "F".charCodeAt(0))
                  event.preventDefault()
                  event.target.dispatchEvent(newEvent)
           }
        }-*/;

    } 

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_frm/thread/e8c0d88cc3d0fca4

Reported by gwt.team.vli on 2006-09-20 05:09:49

Stop/Cancel event propagating

Originally reported on Google Code with ID 11

GWT Release:
1.1.10

Detailed description:
Currently, there is no simple way to stop/cancel event propagating.  The
typical case is onClick event: for example if you have a CheckBox on
FocusPanel, the onClick event is fired twice, once on CheckBox and once on
FocusPanel.  It would be nice if GWT provides a simple way for developers
to cancel certain event.

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/a385736d090d80ee/
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/8a526c537ff25d58/

Reported by gwt.team.vli on 2006-09-15 23:25:45

RPC servlet mounted at same location as app's top-level package hangs hosted mode

Originally reported on Google Code with ID 9

GWT Release: 1.1.10

Detailed description:
If you have a servlet mounted at "/test" and the top-level package name for
your application is "test", your app will fail to load in hosted mode.

Workaround if you have one:
Mount your servlet at a different location or change your top-level package
name.

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/32037f82ce521133

Reported by gwt.team.scottb on 2006-09-15 22:16:50

Serializer.getSerializationSignature() should not throw exceptions

Originally reported on Google Code with ID 23

GWT Release: 1.1.10

Detailed description:
Serializer.getSerializationSignature is not specified to throw an
exception, but it currently throws checked exceptions from JSNI.  It should
simply return the original typeName of an error occurs.

Reported by gwt.team.scottb on 2006-09-19 17:47:08

Checkbox and radio button lost state when hidden

Originally reported on Google Code with ID 43

GWT Release:
1.10
Browser or OS version (if applicable):
IE
Detailed description:
Checkboxes and radio buttons lose their state when the panel they are
 on is hidden and then redisplayed.
Example code showing the problem (strongly preferred):
public void onModuleLoad() {
   final HorizontalPanel p1 = new HorizontalPanel();
   CheckBox a= new CheckBox("by default, not checked");
   p1.add(a);
   CheckBox checked = new CheckBox("is checked");
   checked.setChecked(true);
   p1.add(checked);

   final RootPanel p = RootPanel.get();
   p.add(p1);

   Button b = new Button("detach/re-atach");
   b.addClickListener(new ClickListener(){
     public void onClick(Widget sender) {
      p.remove(p1);
      p.add(p1);
     }

   });
  p.add(b);

 }
Workaround if you have one:

Links to the relevant discussion group topics (optional):

Reported by gwt.team.ecc on 2006-09-20 10:55:53

Setting table cell widget height=100% is ignored on IE

Originally reported on Google Code with ID 44

GWT Release:
1.1.10
Browser or OS version (if applicable):
IE
Detailed description:
On IE, cells in a table must be set to 100% height before IE will respect
the widget's directive to be set to 100% height.

Example code showing the problem (strongly preferred):
import com.google.gwt.core.client.EntryPoint; 
import com.google.gwt.user.client.ui.Button; 
import com.google.gwt.user.client.ui.FlexTable; 
import com.google.gwt.user.client.ui.RootPanel; 
/** 
 * Entry point classes define <code>onModuleLoad()</code>. 
 */ 
public class ImageViewer implements EntryPoint { 
        public void onModuleLoad() { 
                final RootPanel rootPanel = RootPanel.get(); 
                { 
                        final FlexTable flexTable = new FlexTable(); 
                        rootPanel.add(flexTable, 50, 20); 
                        flexTable.setCellSpacing(10); 
                        flexTable.setBorderWidth(5); 
                        { 
                                final Button button = new Button(); 
                                flexTable.setWidget(0, 0, button); 
                                flexTable.getCellFormatter().setWidth(0, 0,
"156"); 
                                button.setText("Button 0-0"); 
                        } 
                        { 
                                final Button button = new Button(); 
                                flexTable.setWidget(1, 0, button); 
                                button.setText("Button 1-0"); 
                        } 
                        { 
                                final Button button = new Button(); 
                                flexTable.setWidget(0, 1, button); 
                                button.setHeight("100%"); 

flexTable.getFlexCellFormatter().setRowSpan(0, 1, 2); 
                                button.setText("Button 0-1"); 
                        } 
                } 
        } 



Workaround if you have one:
set the cell's height first
Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/98b50e6faaea8f16

Reported by gwt.team.ecc on 2006-09-20 11:01:29

UIObject.setStyleName fails for styles which are proper subsets

Originally reported on Google Code with ID 47

GWT Release:
1.1.10
Browser or OS version (if applicable):
all
Detailed description:
A style will incorrectly match an existing style if the new style is a
subset of the existing style.

Example code showing the problem (strongly preferred):

 Label label = new Label();
 label.addStyleName( "style1" );
 label.addStyleName( "style" );

The resulting className will be "style1" when it should be "style1 style1.

The offending line is:

   // See if 'style' is already present.
   int idx = oldStyle.indexOf(style);
Workaround if you have one:

Links to the relevant discussion group topics (optional):

Reported by gwt.team.ecc on 2006-09-20 11:13:26

RPC Proxy classes don't handle exceptions properly in hosted mode

Originally reported on Google Code with ID 22

GWT Release: 1.1.10

Detailed description:
The generated Proxy classes in RPC currently catch SerializationException.
 However, exceptions thrown in hosted mode most often come through wrapped
as a RuntimeException due to intermediate JSNI code.

We need to either make hosted mode properly throw checked exceptions out of
JSNI, or catch RuntimeException in the generated classes.

Reported by gwt.team.scottb on 2006-09-19 17:44:15

Online developer guide still references Composite.setWidget() (deprecated), should use initWidget()

Originally reported on Google Code with ID 34

GWT Release:
1.1.10
Browser or OS version (if applicable):

Detailed description:
Composite requires a call to initWidget() instead of setWidget(), but the
online developer guide still refers to the deprecated method.

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/592c671a1c85b97f

Reported by gwt.team.vli on 2006-09-20 06:27:26

Javadoc version of documentation missing images

Originally reported on Google Code with ID 20

GWT Release: 1.1.10

Detailed description:
The Javadoc version of the class API documentation doesn't include images
and other resources.  It would be nice if it did.

Reported by gwt.team.scottb on 2006-09-19 17:33:44

Internal Compiler Error calling instance-qualified static method

Originally reported on Google Code with ID 6

GWT Release: 1.1.10

Detailed description:
In certain cases, calling a static method through an instance variable can
generate an internal compiler error.

Example:
class Class1 {
   public static void foo (String s) {...}
}
class Class2 {
   final Class1 c1 = new Class1();
   ......
   b.addClickListener (new ClickListener() {
      public void onClick (Widget sender) {
        c1.foo ("hello");
      }
   });
}

Workaround:
Qualify the call with the name of the class.

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/9359791f13ebb841

Reported by gwt.team.scottb on 2006-09-15 18:50:13

Predefined constants for DOM & CSS attributes

Originally reported on Google Code with ID 26

Detailed description:

Predefined constants for css attribute names will help reduce the syntax error.

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/d63d21ae0c5ed909

Reported by gwt.team.vli on 2006-09-20 05:28:01

RemoteServiceServlet fails to locate servce interfaces defined in superclasses

Originally reported on Google Code with ID 50

GWT Release: 1.0.21, 1.1.0, 1.1.10

Browser or OS version (if applicable):

Detailed description:
The <copde>RemoteServiceServlet</code> implementation does not search its
superclasses when attempting to locate the service interface to handle the
RPC call. 

Therefore it does not find the service interface being requested which
results in a <code>SecurityException</code> being thrown on the server.

Example code showing the problem (strongly preferred):
RPC calls to the <code>MyServiceImpl</code> servlet below will fail with a
<code>SecurityException</code> because the <code>MyService</code> interface
is implemented by its superclass.
<code>
  public interface MyService {
    // code omitted for clarity
  }

  public class MyServiceImplBase extends RemoteServiceServlet implements
MyService {
    // code omitted for clarity
  }

  public class MyServiceImpl extends MyServiceImplBase {
    // code omitted for clarity
  }
</code>

Workaround if you have one:
The <code>MyServiceImpl</code> class can declare that it implements the
<code>MyService</code> interface.  The <code>MyServiceImplBase</code> class
can also be collapsed into the <code>MyServiceImpl</code> class.

<code>
  public interface MyService {
    // code omitted for clarity
  }

  public class MyServiceImplBase extends RemoteServiceServlet implements
MyService {
    // code omitted for clarity
  }

  public class MyServiceImpl extends MyServiceImplBase implements MyService {
    // code omitted for clarity,
    // This class does not actually implement any of the
<code>MyService</code> methods.
  }
</code>

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/f4e4bed238f0d56d

Reported by gwt.team.mmendez on 2006-09-20 17:11:25

GWT Compiler flag to only compile for one browser

Originally reported on Google Code with ID 42

GWT Release:
1.1.10

Browser or OS version (if applicable):

Detailed description:

Reporter asks to be able to limit compilation to a specific browser to
speed up the development/debug cycle, as large projects take significantly
longer to compile.

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/abe66d5d2350bd8e

Reported by gwt.team.vli on 2006-09-20 07:18:12

PopupPanel.setSize() expects a child widget

Originally reported on Google Code with ID 40

GWT Release:
1.1.10

Browser or OS version (if applicable):

Detailed description:
PopupPanel.setSize() always expects a child widget, but on some browsers
one isn't created and sometimes the reporter wishes to show an empty
PopupPanel.

Example code showing the problem (strongly preferred):

Workaround if you have one:
Add an empty Label widget.

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/df0d52407b44832f

Reported by gwt.team.vli on 2006-09-20 07:11:03

Make Tree easier to iterate

Originally reported on Google Code with ID 30

GWT Release:
1.1.10

Browser or OS version (if applicable):

Detailed description:

Tree class has a set of function to access tthe root nodes while subsequent
levels of the tree are accessed through TreeItem.

It would be nice to have an easier way to iterate through the Tree.

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):

Reported by gwt.team.vli on 2006-09-20 05:56:50

Tree getAbsoluteLeft()/getAbsoluteTop() doesn't return correct values?

Originally reported on Google Code with ID 39

GWT Release:
1.1.10

Browser or OS version (if applicable):

Detailed description:

Reporter sets position of tree to 5,5 in root container, but Tree reports
its position as 5,25 when queried.

Example code showing the problem (strongly preferred):

/**
 * Entry point classes define <code>onModuleLoad()</code>.
 */
public class ImageViewer implements EntryPoint {
        private CheckBox m_checkBox;
        private Tree m_tree;
        public void onModuleLoad() {
                RootPanel rootPanel = RootPanel.get();
                {
                        m_tree = new Tree();
                        rootPanel.add(m_tree, 5, 5);
                }
                {
                        final Button button = new Button();
                        rootPanel.add(button, 192, 225);
                        button.addClickListener(new ButtonClickListener());
                        button.setText("Show tree location");
                }
                {
                        m_checkBox = new CheckBox();
                        rootPanel.add(m_checkBox, 200, 5);
                        m_checkBox.setText("New CheckBox");
                }
                {
                        final Button showCheckboxLocationButton = new Button();
                        rootPanel.add(showCheckboxLocationButton, 192, 260);
                        showCheckboxLocationButton.addClickListener(new
ShowCheckboxLocationButtonClickListener());
                        showCheckboxLocationButton.setText("Show CheckBox
location");
                }
        }
        private class ButtonClickListener implements ClickListener {
                public void onClick(Widget sender) {
                        System.out.println("tree location: " +
m_tree.getAbsoluteLeft() + ",
" + m_tree.getAbsoluteTop());
                }
        }
        private class ShowCheckboxLocationButtonClickListener implements
ClickListener {
                public void onClick(Widget sender) {
                        System.out.println("checkBox location: "
                                + m_checkBox.getAbsoluteLeft()
                                + ", "
                                + m_checkBox.getAbsoluteTop());
                } 
}

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/d9408e43f15b4053

Reported by gwt.team.vli on 2006-09-20 06:59:11

TabBar::selectTab() no longer accepts a -1

Originally reported on Google Code with ID 27

GWT Release:
1.1.0

Browser or OS version (if applicable):

Detailed description:
With the new release of GWT 1.1.0, the user is not able to call
TabBar::selectTab(-1) to unselect a tab. The user was able to use this with
the previous version.

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/873c5341f5b4d656/

Reported by gwt.team.vli on 2006-09-20 05:33:25

Class without default constructor cannot be entry point, even if onModuleLoad() is static

Originally reported on Google Code with ID 17

GWT Release: 1.1.10

Detailed description:
GWT supports having an entry point class with a static onModuleLoad(). 
However, entry point classes are automatically rebound (that is, they are
treated as if GWT.create() was called), and if the class has no default
constructor, the rebind process fails.

Example:

class Foo {
  public Foo(String name) { }
  public static void onModuleLoad() { }
}

Workaround:

Add a default constructor to the class.

Reported by gwt.team.scottb on 2006-09-19 17:19:19

Long.parseLong, Double.parseDouble, Integer.parseInt are too lenient

Originally reported on Google Code with ID 7

GWT Release: 1.1.10

Detailed description:
The Java implementation of Long.parseLong() throws an exception if the
format is not correct:

 "16316" OK
 "65131asd" exception
 "16dasddsad" exception
 "a1" exception

However, GWT's Long.parseLong() is implemented in JavaScript and performs
as follows

"16316" OK
 "65131asd" OK returns 65131
 "16dasddsad" OK returns 16
 "a1" exception

This is also true for Double.parseDouble, Integer.parseInt, etc.

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/c31d2f239820686c

Reported by gwt.team.scottb on 2006-09-15 18:54:45

setCookie() doesn't work on IE/Windows?

Originally reported on Google Code with ID 38

GWT Release:
1.1.10

Browser or OS version (if applicable):
IE / Windows

Detailed description:

The reporter claims that setCookie() and GWT Date class when used with a
long argument doesn't work on Windows.

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/d11a93f454cbfec1

Reported by gwt.team.vli on 2006-09-20 06:45:38

Lack of java.io.Serializable hurts interoperability

Originally reported on Google Code with ID 21

GWT Release: 1.1.10

Detailed description:
GWT doesn't include a class definition for java.io.Serializable.  This is
to avoid confusion with GWT's built-in serialization mechanisms.  However,
not having a definition causes compile errors when trying to use a single
set of classes that are both IsSerializable and Serializable.  Several
users have requested this.

Workaround if you have one:
Add an empty Serializable interface to gwt-user.jar as
com/google/gwt/emul/java/io/Serializable.java

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/8fe5d325263460e1
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/30b7a90432d0ced8

Reported by gwt.team.scottb on 2006-09-19 17:39:41

TextArea.getSelectedText()

Originally reported on Google Code with ID 28

GWT Release:
1.1.0

Browser or OS version (if applicable):
IE

Detailed description:
Getting the caret position in IE seems to be a hard problem. 

Example code showing the problem (strongly preferred):
public native int getTextAreaCursorPos(Element elem) /*-{
    try {
      var tr = elem.document.selection.createRange();
      var tr2 = tr.duplicate();
      tr2.moveToElementText(elem);
      tr.setEndPoint('StartToStart', tr2);
      return tr.text.length;
    }
    catch (e) {
      return 0;
    }
  }-*/; 

Workaround if you have one:
http://www.bazon.net/mishoo/articles.epl?art_id=1292

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/ac701423c29eb9ef/

Reported by gwt.team.vli on 2006-09-20 05:41:29

GWT hosted mode DOM inspector desired

Originally reported on Google Code with ID 4

Detailed description:
Being able to inspect the DOM within hosted mode would be very handy for
development.  Such a feature would consist of a bridge to access the DOM
within Hosted mode as an XML Document bia the GWT XML API, plus some sort
of UI....

Example code showing the problem (strongly preferred):

Workaround if you have one:
Use the DOM inspector that is available with Firefox in web mode, or use
DOMInspector for IE under hosted mode.


Links to the relevant discussion group topics (optional):
From
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/6bef5fad2f05e96
 --

It would be very helpful to have this feature then we know *what's
 going on in the browser* at real time.

Recently I"m working on a large-scale application. The code is quite
 complex so that I cannot view the whole HTML code through variable
 monitor and it's also not convenient to use xxxx-compile.cmd generate
 scripts very often ( for small gwt app I do this so that I can view my
 page in IE or Firefox and use a DOM inspecting tool to view the actual
 DOM tree) since it will take very long time.

I understand GWT is supposed to liberate developers from dealing with
 complex HTML tags. But honestly I have to inspect raw html code when
 things go wrong because that helps me locate the problem more quickly.

I want to know how other developers debug their code especially when
 the app is quite complex.

Reported by gwt.team.hcc on 2006-09-15 18:36:03

Split release notes out of index.html into a new file

Originally reported on Google Code with ID 8

This will make it easier to update the code site's release notes, will keep
our index.html more stable, and is more consistent with how most projects
do it.

Reported by gwt.team.scottb on 2006-09-15 19:05:46

Minimum Browser Requirements - doc improvement

Originally reported on Google Code with ID 36

GWT Release:
1.1.10

Browser or OS version (if applicable):

Detailed description:
The GWT documentation does not specify minimum browser requirements.

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/d17259630b8e500e

Reported by gwt.team.vli on 2006-09-20 06:34:38

OnFocus events tests

Originally reported on Google Code with ID 13

GWT Release:
1.10
Browser or OS version (if applicable)
All
Detailed description:
Mat Gessel supplied a great focus test which exposed some problems with the
onfocus event. This bug is tracking those problems.
Problems
 CheckBox,Mozilla/Opera: fixed
 RadioButton, Mozilla/Opera: fixed
 ListBox, all:fixed
 Frame/NamedFrame: Cannot be fixed, upcoming API change
 Tree: still broken


Example code showing the problem (strongly preferred):
http://www.asquare.net/gwt/bugs/

Workaround if you have one:
None

Links to the relevant discussion group topics (optional):

Reported by gwt.team.ecc on 2006-09-18 12:01:26

---

- _Attachment: [](https://storage.googleapis.com/google-code-attachments/google-web-toolkit/issue-13/comment-0/)_ - _Attachment: [](https://storage.googleapis.com/google-code-attachments/google-web-toolkit/issue-13/comment-0/)_

Setting content area size of DialogBox to 100%,100% does not fill entire area.

Originally reported on Google Code with ID 41

GWT Release:
1.1.10

Browser or OS version (if applicable):

Detailed description:
  Setting an AbsolutePanel to a size of 100%,100% and placing it inside of
a PopupPanel causes it to fill all of the space of the PopupPanel, but
placing the same AbsolutePanel inside of a DialogBox does not fill all of
the space of the DialogBox.

Example code showing the problem (strongly preferred):
import com.google.gwt.user.client.ui.AbsolutePanel;
import com.google.gwt.user.client.ui.DialogBox;
public class MyDialog extends DialogBox {
        public MyDialog() {
                {
                        final AbsolutePanel absolutePanel = new
AbsolutePanel();
                        setWidget(absolutePanel);
                        absolutePanel.setSize("100%", "100%");
                }
        } 
}

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/6942d627ae6ffe29

Reported by gwt.team.vli on 2006-09-20 07:14:45

Grid and FlexTable are somewhat slow

Originally reported on Google Code with ID 12

GWT Release:
1.10
Browser or OS version (if applicable):
All
Detailed description:
The goal is to speed up FlexTable and Grid. 
Currently we are getting between a 50%-2000% speed improvement on selected
 benchmarks. 

Example code showing the problem (strongly preferred):
public void createLargeGrid() {
   long s = System.currentTimeMillis();
   FlexTable r = new FlexTable();

   r.setBorderWidth(2);
   for (int i = 0; i < ROWS; i++) {
     r.getRowFormatter().addStyleName(0, "MyRowStyle");
     for (int j = 0; j < COLUMNS; j++) {
       r.getCellFormatter().setStyleName(i, j, "MyCellStyle");
       r.setText(i, j, "row:" + i + " col:" + j);
     }
   }
   String msg = "Creating the table took " + (System.currentTimeMillis() - s)
     + "milliseconds";
   Window.alert(msg);
   s = System.currentTimeMillis();
   for (int i = 0; i < ROWS; i++) {
     r.getRowFormatter().getStyleName(0);
     for (int j = 0; j < COLUMNS; j++) {
       r.getCellFormatter().getStyleName(i, j);
       r.getText(i, j);
     }
   }
   msg = "Reading the table took " + (System.currentTimeMillis() - s)
     + "milliseconds";
   Window.alert(msg);
   RootPanel.get().add(r);
 }

Workaround if you have one:
None

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/ebc4bad957e2509b/

Reported by gwt.team.ecc on 2006-09-18 11:52:40

FocusPanel firing ONMOUSEOUT event too many times

Originally reported on Google Code with ID 16

GWT Release:
1.10
Browser or OS version (if applicable):
Firefox
Detailed description:
The problem is when FocusPanel contain more than on child
widget (more precisely, when the FocusPanel contain an element which
contain other widgets). When the mouse go over a child widget of the
focus panel, an ONMOUSEOUT event is fired event if we are still over
the FocusPanel. 
Example code showing the problem (strongly preferred):
/**
 * Entry point classes define <code>onModuleLoad()</code>.
 */
public class MyApp implements EntryPoint {

        /**
         * This is the entry point method.
         */
        public void onModuleLoad() {
                MouseAwarePanel mouseAwarePanel = new MouseAwarePanel();
                VerticalPanel vpanel = new VerticalPanel();
                Label test1 = new Label("test1");
                Label test2 = new Label("test2");
                Label test3 = new Label("test3");
                vpanel.add(test1);
                vpanel.add(test2);
                vpanel.add(test3);
                mouseAwarePanel.add(vpanel);
                RootPanel.get("slot1").add(mouseAwarePanel);

        }

}

class MouseAwarePanel extends SimplePanel {

        public MouseAwarePanel() {
                super();
                sinkEvents(Event.ONMOUSEOUT);
        }

        public void onBrowserEvent(Event event) {
                switch (DOM.eventGetType(event)) {
                case Event.ONMOUSEOUT:
                        // Only fire the mouseLeave event if it's actually
leaving this
                        // widget.
                        Element to = DOM.eventGetToElement(event);
                        if (to == null)
                                Window.alert("On firefox, eventGetToElement
returned null");
                        break;
                }
        } 
Workaround if you have one:

Links to the relevant discussion group topics (optional):

Reported by gwt.team.ecc on 2006-09-18 12:17:27

Include a standard Context Menu in GWT

Originally reported on Google Code with ID 24

Detailed description:
There are several requests to include standard Context Menu in GWT.
Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/4a9b208421511fda/

Reported by gwt.team.vli on 2006-09-20 04:42:08

DOMImplStandard.getParent does not check to see if parent == null

Originally reported on Google Code with ID 2

GWT Release:
1.1.0

Browser or OS version (if applicable):
all

Detailed description:
    DOMImplStandard.getParent does not check to see if parent == null
before checking type.

Reported by gwt.team.hcc on 2006-09-15 18:29:02

Absolute positions in a ScrollPanel differ between IE and FF

Originally reported on Google Code with ID 46

GWT Release:
1.1.10
Browser or OS version (if applicable):
FF/IE
Detailed description:
On Firefox the parent scroll panel position is computed into the panel, on
IE it is not.
Example code showing the problem (strongly preferred):

Workaround if you have one:
public static ScrollPanel findParentScrollPanel(Widget widget) 
  { 
    if (widget == null) return null; 
    if (widget instanceof ScrollPanel) 
    { 
      return (ScrollPanel)widget; 
    } 
    Widget parent = widget.getParent(); 
    return findParentScrollPanel(parent); 
  } 


  mouse handler... 


    if (isGecko()) // Bug workaround for Gecko in scroll panels 
    { 
      ScrollPanel scroll = WidgetUtil.findParentScrollPanel(this); 
      if (scroll != null) 
      { 
        x -= scroll.getHorizontalScrollPosition(); 
        y -= scroll.getScrollPosition(); 
      } 
    } 



Links to the relevant discussion group topics (optional):

Reported by gwt.team.ecc on 2006-09-20 11:08:58

FocusPanel firing extra ONMOUSEOUT events

Originally reported on Google Code with ID 45

GWT Release:
1.1.10
Browser or OS version (if applicable):
IE
Detailed description:
The problem is when FocusPanel contain more than on child 
widget (more precisely, when the FocusPanel contain an element which 
contain other widgets). When the mouse go over a child widget of the 
focus panel, an ONMOUSEOUT event is fired event if we are still over 
the FocusPanel.  Note, this seems to apply toe Tree as well.



Example code showing the problem (strongly preferred):
** 
 * Entry point classes define <code>onModuleLoad()</code>. 
 */ 
public class MyApp implements EntryPoint { 


        /** 
         * This is the entry point method. 
         */ 
        public void onModuleLoad() { 
                MouseAwarePanel mouseAwarePanel = new MouseAwarePanel(); 
                VerticalPanel vpanel = new VerticalPanel(); 
                Label test1 = new Label("test1"); 
                Label test2 = new Label("test2"); 
                Label test3 = new Label("test3"); 
                vpanel.add(test1); 
                vpanel.add(test2); 
                vpanel.add(test3); 
                mouseAwarePanel.add(vpanel); 
                RootPanel.get("slot1").add(mouseAwarePanel); 


        } 



} 


class MouseAwarePanel extends SimplePanel { 

        public MouseAwarePanel() { 
                super(); 
                sinkEvents(Event.ONMOUSEOUT); 
        } 


        public void onBrowserEvent(Event event) { 
                switch (DOM.eventGetType(event)) { 
                case Event.ONMOUSEOUT: 
                        // Only fire the mouseLeave event if it's actually
leaving this 
                        // widget. 
                        Element to = DOM.eventGetToElement(event); 
                        if (to == null) 
                                Window.alert("On firefox, eventGetToElement
returned null"); 
                        break; 
                } 
        } 



Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/22216c19601c0f10

Reported by gwt.team.ecc on 2006-09-20 11:05:43

ListBox addItem of 100 or more has performance problems.

Originally reported on Google Code with ID 49

GWT Release:
1.1.10
Browser or OS version (if applicable):
Firefox
Detailed description:
ListBox.addItem(String) has poor performance when you are adding
more than 100 items to the list because of an n^2 algorithm.
Example code showing the problem (strongly preferred):
public void addTiming(int num) {
    ListBox b = new ListBox();
    RootPanel.get().add(b);
    resetTimer();
    for (int i = 0; i < num; i++) {
      b.addItem("item" + i,"i:" + i);
    }
    timing("add(" + num + ")");
  }
}
Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/e19fc5ba46008f16

Reported by gwt.team.ecc on 2006-09-20 11:33:22

Obtain actual index of the visible StackPanel

Originally reported on Google Code with ID 29

GWT Release:
1.1.10

Detailed description:

It would be nice to have some method to obtain directly the actual index of
the visible panel. 

Workaround if you have one:
public class ExtendedStackPanel extends StackPanel {

private int stackIndex = 0;

public void showStack( int index ) {
               stackIndex = index;
               super.showStack(index);
}

public int getStackIndex(){
               return stackIndex;
}

}

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/c51d17d8d9f38c2a/

Reported by gwt.team.vli on 2006-09-20 05:45:57

Internal Compiler Error referencing static final null field

Originally reported on Google Code with ID 5

GWT Release: 1.1.10

Detailed description:
Referencing a static final field that is set to null can cause an internal
compiler error in cases where the class itself would never be initialized.

Example:

public class Hello {
 public void onModuleLoad() {
   Window.alert(Foo.foo);
 }
}
class Foo {
 public static final String foo = null;
}

Workaround if you have one:
Use an empty string instead of null for Strings, or make the field non-final.

Reported by gwt.team.scottb on 2006-09-15 18:46:21

Support arbitrary widgets to Tree and TabBar

Originally reported on Google Code with ID 10

GWT Release: 1.1.10

Detailed description:
GWT doesn't support arbitary widgets to Tree and TabBar.  It is a nice
feature to have.

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/75010e8df04bb3f0/

Reported by gwt.team.vli on 2006-09-15 23:17:09

Bug in StackPanel remove

Originally reported on Google Code with ID 48

GWT Release:
1.1.10
Browser or OS version (if applicable):
All
Detailed description:
Remove in StackPanel does not correctly implement the remove method.
Example code showing the problem (strongly preferred):

Workaround if you have one:
public class BugStackPanel extends Sink {
    public static SinkInfo init() {
        return new SinkInfo("BugStackPanel",
                "GWT has bugs") {
            public Sink createInstance() {
                return new BugStackPanel();
            }
        };
    }


    public BugStackPanel() {
        FlowPanel fp = new FlowPanel();
        final MyStackPanel sp = new MyStackPanel();
        final Button b=new Button("Button");
        final Button b2=new Button("Button2");
        final Button b3=new Button("Button3");
        sp.add(b, "Section1");
        sp.add(b2, "Section2");
        sp.add(b3, "Section3");
        final Button remove=new Button("Remove Button 2");
        remove.addClickListener(new ClickListener() {
            public void onClick(Widget widget) {
              sp.remove(b2);
            }
        });
        fp.add(sp);
        fp.add(remove);
        initWidget(fp);
    }

    public void onShow() {
    }
    public void foo()
    {

    }
}

Links to the relevant discussion group topics (optional):

Reported by gwt.team.ecc on 2006-09-20 11:17:16

Update exception messages that refer to "setWidget()" instead of "initWidget()"

Originally reported on Google Code with ID 31

GWT Release:
1.1.10

Browser or OS version (if applicable):

Detailed description:
When extending a Composite without invoking the initWidget() method, in
hosted mode (possibly in webmode too?) this exception is thrown:

java.lang.IllegalStateException: setWidget() was never called...

while setWidget() is deprecated and you probably mean initWidget().

Further, in Composite.java, the following code needs to be changed too:

protected void initWidget(Widget widget) {
   // Make sure the widget is not being set twice.
   if (this.widget != null) {
     throw new IllegalStateException("Composite.setWidget() may only be "
       + "called once.");
   }

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/3f2a5ce338ad7188

Reported by gwt.team.vli on 2006-09-20 06:01:45

Compiler bug binding method call from inner class causes infinite loop

Originally reported on Google Code with ID 18

GWT Release: 1.1.10

Detailed description:
In certain cases, calling a method on an outer class through a qualified
"this" reference from an anonymous inner class can erroneously target the
method on the calling class.  This happens, for example, when the method is
part of an interface, and both the inner and outer class both implement the
interface.

Example:

This class gets into an infinite loop in web mode.

public class Hello implements EntryPoint {

 public void onModuleLoad() {
   new AsynchronousCommand() {
     public void makeAsynchronousCall(AsyncCallback callback) {
       callback.onFailure(null);
     }

     public void onFailure(Throwable caught) {
       Window.alert("onFailure");
     }

     public void onSuccess(Object result) {
       Window.alert("onSuccess");
     }
   }.execute();
 }
}

abstract class AsynchronousCommand implements AsyncCallback {
 public abstract void makeAsynchronousCall(AsyncCallback callback);

 public final void execute() {
   makeAsynchronousCall(new AsyncCallback() {
     public void onFailure(Throwable caught) {
       AsynchronousCommand.this.onFailure(caught);
     }

     public void onSuccess(Object result) {
       AsynchronousCommand.this.onSuccess(result);
     }
   });
 }
}

Workaround:

Convert the anonymous class to a static, nested named class.

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/eee2599c62fe92de

Reported by gwt.team.scottb on 2006-09-19 17:25:50

XPATH and XSLT support for GWT XML support

Originally reported on Google Code with ID 3

GWT Release:
1.1.0

Browser or OS version (if applicable):
all

Detailed description:
  Users want XSLT and XPATH in GWT xml support.

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/e77f05af3ea4d732

Reported by gwt.team.hcc on 2006-09-15 18:31:04

GWT 1.1 doesn't work for file:// URLs in Safari

Originally reported on Google Code with ID 35

GWT Release:
1.1.10

Browser or OS version (if applicable):
Safari 2.0.4

Detailed description:
If you load a GWT application using a file:/// URL from the local disk
instead of from an HTTP server, the application fails to load correctly.

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/d17edaab34ab4272

Reported by gwt.team.vli on 2006-09-20 06:32:25

Double and Float missing constants

Originally reported on Google Code with ID 19

GWT Release: 1.1.10

Detailed description:
Some pieces of the Double and Float API are missing.

Float.NAN, Double.NAN
Float.POSITIVE_INFINITY, Double.POSITIVE_INFINITY, 
Float.NEGATIVE_INFINITY, Double.NEGATIVE_INFINITY
Float.intBitsToFloat(), Double.longBitsToDouble()

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/cf1595217279049

Reported by gwt.team.scottb on 2006-09-19 17:32:24

Date.toString() returns different format in IE vs FF

Originally reported on Google Code with ID 37

GWT Release:
1.1.10

Browser or OS version (if applicable):
Firefox

Detailed description:
The string returned by Date.toString() in IE adheres to the format
described in Sun's documentation for java.util.Date, but the format of the
String returned in Firefox does not.

Example code showing the problem (strongly preferred):

Workaround if you have one:

Links to the relevant discussion group topics (optional):
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/953adf5b69894073

Reported by gwt.team.vli on 2006-09-20 06:38:58