Sign in
gwt
/
gwt
/
26cd1b4e57916f8615956cf3f4796831021a4982
/
reference
aa1db7f
Code museum now points to the GWT.css in com.google.gwt.user instead of maintaining its own copy.
by jlabanca@google.com
· 17 years ago
9b3d4d8
Fixed an issue where the DeckPanel flickers in IE7 when switching from one widget to another because the new widget is completely visible for an instant, even though its container is set to a height of 0px. This patch starts the height at 1px instead of 0px, which corrects the problem. This patch also uses a new method to determine if the deck panel has a fixed height, which in turn determines how we do the animation. The old method wasn't 100% accurate in some common use cases, but the new method should be.
by jlabanca@google.com
· 17 years ago
56db572
Fixed a IE7 bug in the TreeItem animation where the children would be completely visible for an instant when expanding the children.
by jlabanca@google.com
· 17 years ago
cb03bc8
Upgrading museum to have default css and adding issue 1488 (not yet added to default museum as it has not been fixed)
by gwt.team.ecc
· 17 years ago
dca3fb1
Upgrading museum to have default css and adding issue 1488 (not yet added to default museum as it has not been fixed)
by gwt.team.ecc
· 17 years ago
837d8c7
Upgrades to default museum to clean up checkstyle errors and add two new issues.
by gwt.team.ecc
· 17 years ago
fb085c3
Added a test for issue 1897 "Attaching and detaching a RichTextArea too fast crashes GWT" to the museum.
by jlabanca@google.com
· 17 years ago
8d5c958
Added issue 2331 to museum.
by gwt.team.ecc
· 17 years ago
0cec8b5
Modified bug museum to allow bugs to be sliced and diced more easily by
by gwt.team.ecc
· 17 years ago
27d808b
Modified bug museum to allow bugs to be sliced and diced more easily by
by gwt.team.ecc
· 17 years ago
182318e
Moved all the code around, and SVN is having a fit, so pushing updates peace meal.
by gwt.team.ecc
· 17 years ago
8bf96e1
Modified the code museum to load all issues at starup and allow the user to select one at a time. Style sheets are loaded dynamically to avoid conflicts in style names.
by jlabanca@google.com
· 17 years ago
6fe8edd
Initial commit towards adding a new "reference" section for the project's own reference over time, including an HTML encyclopedia (to easily reproducible/check HTML behavior across browsers) and a "code museum" that will house little code snippets that we create when testing issues, etc. The point is to accumulate a set of reference materials we can continue to keep around instead of editing Hello locally and throwing it away :-)
by bruce@google.com
· 17 years ago