View Full Version : Grid (?) causes browser address change

3 Jun 2014, 2:34 PM
I want to integrate a GXT-based view that includes mainly a Grid (http://docs.sencha.com/gxt/3.1.0-beta/javadoc/index.html) into an existing GWT application.

The grid contains some custom Menus (http://docs.sencha.com/gxt/3.1.0-beta/javadoc/index.html), e.g. accessible from each of the Grid's cells.
The GWT application uses GWT's history menchanism (http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsHistory.html).
After integration, the access of the Menu's causes the browser's address to change, e.g.

xxxx://.../?gwt.codesvr=...#MyPlace:param=value -> xxxx://.../?gwt.codesvr=...#
This leads the History mechanism to load a defaultPlace (http://www.gwtproject.org/javadoc/latest/com/google/gwt/place/shared/PlaceHistoryHandler.html), which is not the desired behavior.
At first I thought GXT's stateful feature (http://www.sencha.com/blog/ext-gwt-3-0-state-api/) might cause the address change in order to maintain state information there. However, the grid is configured stateless and the default Provider (http://docs.sencha.com/gxt/3.1.0-beta/javadoc/index.html) used inStateManager (http://docs.sencha.com/gxt/3.1.0-beta/javadoc/index.html) is CookieProvider (http://docs.sencha.com/gxt/3.1.0-beta/javadoc/index.html).

Is there any other GXT feature that I am not aware of that could cause this kind of behavior?
I don't know how to approach debugging this. Any hints on this part?

Andreas Samjeske
12 Jun 2014, 12:06 AM
I am using GWT-History support and GXT grids in many ways as well. Nothing odd happens here.
I think the Menus are to blame, which has been your assumption anyway.

I guess you have to share more info or condense it to a small example.