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 this element will cause a row unhover event. This is particularly a problem if the element is shown/dismissed based on row hovering (causing a flickring effect).

Also include the original browser event in the RowHoverEvent in case the user needs more information about the original event.

Review at http://gwt-code-reviews.appspot.com/1546803

Review by: jlabanca@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10660 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Introduces BrowserEvents string constants

Review at http://gwt-code-reviews.appspot.com/1550803

Review by: jlabanca@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10661 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Add a support for header builder to return row index for multi-row
header/footer.

Review at http://gwt-code-reviews.appspot.com/1555803

Review by: jlabanca@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10662 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Enable FF6 Plugin in MissingPlugin Page.

Review at http://gwt-code-reviews.appspot.com/1551803

Review by: rjrjr@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10663 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Allow @defs with multiple values

Review at http://gwt-code-reviews.appspot.com/1557803

Review by: rjrjr@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10667 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Makes sure all attributes from the PotentialElement can be inherited
by an ElementBuilder.

Review at http://gwt-code-reviews.appspot.com/1556803

Review by: rjrjr@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10670 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Fix name clash between RequestContext and the FindRequest impl interface.

I think this was only able to compile due to a javac bug. When I
reinstalled eclipse today (don't ask, just don't ask), this line
started failng with:

Name clash: The method find(EntityProxyId<?>) of type FindRequest has the same erasure as find(EntityProxyId<P>) of type RequestContext but does not override it

Installing a fresh OpenJDK showed the same fail in an ant build.

Review at http://gwt-code-reviews.appspot.com/1559803

Review by: cromwellian@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10671 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Rolling back 24166710. It's broken on IE7/WinXP.

Review by: rjrjr@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10672 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Exporting a map of obfuscated CSS names to full class names into a build
artifact CSV file. This will allow CSS names to be found in the DOM for
frontend testing.

Review by: unnurg@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10675 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Gives CellTable an option to disable colgroup and/or don't attach the message
panel. Disabling both leads to 50% faster layout time in IE (about 25% each). The side effects are

1. Disabling colgroup will break fixed layout table with explicitly set column width, and when styles are added to colgroup element. Therefore this is turned off by default. Various checks are added to make sure setColumnWidth and setTableLayoutFixed(true) are not called when colgroup is disabled.
2. If the message panel is not attached to the table, loading indicator and empty table widget are not displayed. Therefore this optimization is turned off by default as well. A new method is added to get the message panel so that callers can attach it to outside the table element.

Note, disabling colgroup also results in a very small gain in Firefox, Chrome and Safari (around 5%). In addition, having the message panel attached to the table itself actually results in better layout performance in Chrome/Safari. It's recommended to leave inside the table for non-IE browsers.

Review at http://gwt-code-reviews.appspot.com/1557804

Review by: jlabanca@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10676 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Remove entrDepthWatchdog exception reporting.

Review by: rjrjr@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10677 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Fixed issue that was causing ERROR log messages due to duplicate cssmap file names.
Since there may be multiple css resources with the same base subtype (e.g. CssResource), the subtype class is not
guaranteed to be unique. Instead, the qualified resource getter method name is used which is unique.

Review by: unnurg@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10678 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Removing a logging message people are seeing when building with GWT locally.
The GWT compiler is showing inconsistent behavior when compling resources on
forge vs. locally, so the best solution for now is to remove the logging
message so other clients can have clean builds.

Review by: unnurg@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10685 8db76d5a-ed1c-0410-87a9-c151d255dfc7
This change is to update <ui:with> to support setting property values on the
provided type by using a nested <ui:attributes/> element.

There are many times in which non-widget objects are needed in the UiBinder XML.
It's not always convenient to construct these objects in the owner class.  In
some organizations where there are separate teams that write the Java code and
the UiBinder XML, it may not be ideal to distribute, what is considered view
logic/data, across the Java class and the XML file.

This is especially useful for @UiChild methods where one of the parameter types
is a complex type that supplement the Widget being passed to the @UiChild
method.

For example:

<ui:with type="some.LayoutData" field="layoutData">
<ui:attributes left="15" row="3" color="#f0f0f0">
</ui:with>

<foo:SomeWidget>
<foo:child layoutData="{layoutData}">
<foo:ChildWidget />
</foo:child>
</foo:SomeWidget>

Review by rjrjr: http://gwt-code-reviews.appspot.com/1524803/

Review by: rdcastro@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10686 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Segregate JRE Resource tests for more targeted testing

Review at http://gwt-code-reviews.appspot.com/1561804

Review by: skybrian@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10687 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Make client-side JUnit 3 classes available without GWTTestCase.

Review at http://gwt-code-reviews.appspot.com/1564803

Review by: rjrjr@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10689 8db76d5a-ed1c-0410-87a9-c151d255dfc7
In IE, AbstractCellTable replaces a table section by first removing existing tr
elements, and then adding new tr elements one by one. This could really slow
down rendering performance especially if there are many rows to remove and many
rows to add (e.g., 500 rows in one table page, and go to next page).

This change introduces a faster rendering approach where the new html is set to a new
DIV element (that's not attached to the body). Next the entire table section is
swapped with the existing table section. A new interface
TableSectionChangeHandler is introduced so that the subclasses (e.g., CellTable,
DataGrid) can respond to the section swapping event and update their internal
reference to the sections. This is critical since they're usually responsible
for returning the reference for AbstractCellTable to locate the correct table
sections.

When tested in IE9 with IE7 emulate mode, the time to replace 100 rows with 400
new rows in a 30 columns table reduced from 1.4s to 200ms. Tests in other IE
versions return similar results.

Review by: jlabanca@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10690 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Firefox 7 DevMode Plugin

Review at http://gwt-code-reviews.appspot.com/1560803

Review by: conroy@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10693 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Change the superclass of the translatable version of
junit.framework.AssertionFailedError to match the JVM version,
for consistency when catching java.lang.AssertionError in
testing tools.

Fixes issue 6863.

Review at http://gwt-code-reviews.appspot.com/1565803

Review by: rjrjr@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10694 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Fix broken tests.

Review at http://gwt-code-reviews.appspot.com/1566803

Review by: jlabanca@google.com

git-svn-id: http://google-web-toolkit.googlecode.com/svn/trunk@10695 8db76d5a-ed1c-0410-87a9-c151d255dfc7