Search Type: Posts; User: darrellmeyer

Page 1 of 5 1 2 3 4

Search: Search took 0.04 seconds.

  1. I verified the bug in 3.0.6. This is already fixed and the change will go out in 3.0.7. Also, the bug is fixed already in 3.1 which was just released.
  2. The_Jackal I have not been able to reproduce this issue with the original test case and 2.3.0. Can you provide more information and possible a test case that shows the problem you are seeing in...
  3. Thanks for the report! I have opened a bug in our bug tracker.
  4. Replies
    GXT 2.3 will include support for IE10. 2.3 will be available soon.

    The following URL is our 2.3 nightly build. Take a look with IE10 and let us know if you find any issues.
  5. Replies
    We're excited to announce the release of Sencha GXT 3.0.4. This version is avaiable only to our active support subscribers. Support subscribers can download the latest version of GXT from the support...
  6. Thanks for the report! I have opened a bug in our bug tracker.

    I created a new bug thread from your post and moved it to the bugs forum. In the future, please don't report bugs on a general...
  7. I think your best bet will be to keep a list of selected items and update the list each time a selection changed event fires. Each time a selection changed event fires you can compare the current...
  8. Thanks for the report! I have opened a bug in our bug tracker.
  9. The bug is fixed and went out in 3.0.3.
  10. The handler code that executes on key down needs to run deferred to allow the combo to properly end the current edit. Try this code:

    panelA.addDomHandler(new KeyDownHandler() {
  11. I do not believe this bug was fixed in 3.0.1. Looking at:

    The birthday field fires the value change event where it should including...
  12. With
    combo.setValidateOnBlur(false); validation does not run on blur. Therefore, the allow blank validation does not run. When I comment out that line in your example validation works as expected....
  13. SiBurgess - please submit the android issue as a separate bug report.
  14. This bug was fixed in 3.0.1. See I also tested when the button has a menu.

    Let me know if you are still having any issues.
  15. Text is now not selectable for all browsers (the default behavior). You can see the change here:
  16. NestedDivFrameResources defines the images required for the frame. However, the base theme does not provide any images. The interface should be extended to provide implementation. Because images are...
  17. This is now fixed. Changes will go out in 3.0.3.

    public boolean isEnableSourceEditMode()
    public void setEnableSourceEditMode(boolean enable) {}

    public boolean isSourceEditMode()
  18. This bug is now fixed and be validated here:
  19. This bug is now fixed. You can validate the change here:
  20. I have ran the code and see the issue you describe. The primary issue I see is that you have setBorders(true) which is not needed for dialogs which render their own borders. so the getFrameSize call...
  21. Fix can be seen here (this example does have min date set).
  22. This still issue still exists in some versions of FF. HtmlEditor uses the GWT RichTextArea internally which has a known bug. See
  23. I read the report and am not sure what the actual issues is.

    Can you be more specific with what you expect / dont expect. Could yo mean style of the today date, or selected date?

    This is...
  24. Issues is fixed and will go out in 3.0.2. Change can be verified here:
  25. The primary bug was that buttons were not focusable programmatically. This bug has been fixed. You can see the updated code here You...
Results 1 to 25 of 117
Page 1 of 5 1 2 3 4