Success! Looks like we've fixed this one. According to our records the fix was applied for EXTGWT-2591 in a recent build.
  1. #1
    Ext GWT Premium Member
    Join Date
    Dec 2011
    Location
    Earth
    Posts
    243
    Vote Rating
    1
    nbuesing is on a distinguished road

      0  

    Default Dropdown for ComboBox in grid shows up at 0,0 coordinate

    Dropdown for ComboBox in grid shows up at 0,0 coordinate


    Internet Explorer 8
    Windows 7 (64 bit)
    GXT 3.0.2
    GWT 2.4

    I have posted this issue before, and now getting it under different scenario.

    If I go to an editable ComboBox in a grid and type a few characters (in this example "bl") I then tab to the next cell prior to the drop-down showing up (below the cell). When I do that (and get my timing right) the combo-box drop-down shows up at 0,0 (after I leave the cell).

    This is different than the earlier reported but, since the drop-down shows up AFTER the cell LOOSES focus.

    Test case provided.


    ComboBoxPopupAtZeroZeroCoord.png
    Pop-up for cell that I left shows up at 0,0 while the text field (description) which is NOT a drop down has focus.

    ComboBoxDropdownIssue.zip

    Previous Posting : http://www.sencha.com/forum/showthread.php?231087

  2. #2
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,731
    Vote Rating
    90
    Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light

      0  

    Default


    Finally have managed to reproduce this locally, and track down the issue - for some reason I cannot make your steps work, but I can do this:

    * Focus on any combobox in the inline editing grid example, with the cursor in any position, with any amount of characters selected
    * Rapidly type the following:
    *** any few keystrokes - it may match some option in the list, or it may not
    *** tab key
    * Observe that the combobox is blurred, the dropdown is in the upper left, and the focus has moved on.

    The rapid typing turns out to be the key and the clue here - if you get the tab keystroke in before the delayed query task goes off (this query is on a timer to give the user a chance to finish, or to not hammer on the server), the ComboBox will blur and vanish, and after the next field has been made visible and focused, the dropdown will finally appear - but having no ComboBox to use to align it, ends up in the upper left corner. If the tab key doesnt come within the default query delay of half of a second, the bug will not occur - which means that slowly, carefully following instructions leads to the issue not happening.

    I have one simple workaround that has become evident, having found the issue: Remove the delay from the query - since you aren't going to the server (in your example code anyway), the delay will change the user interaction, but will not cause this bug. This should not cause any other issues, since this is a supported part of the ComboBox's options.

    A slightly uglier workaround that doesn't require changing behavior: Subclass ComboBoxCell, override finishEditing to first invoke super, then cancel the dqTask. Because dqTask is private, you'll need JSNI for this fix. I'm still testing this fix, and will update this thread when the fix is in SVN - once it is there, we will continue to test it to ensure there are no other side effects.

  3. #3
    Ext GWT Premium Member
    Join Date
    Dec 2011
    Location
    Earth
    Posts
    243
    Vote Rating
    1
    nbuesing is on a distinguished road

      0  

    Default


    Quote Originally Posted by Colin Alworth View Post
    I have one simple workaround that has become evident, having found the issue: Remove the delay from the query - since you aren't going to the server (in your example code anyway), the delay will change the user interaction, but will not cause this bug. This should not cause any other issues, since this is a supported part of the ComboBox's options.
    Thanks for the suggestion. When I do call comboBox.setQueryDelay(0), it does seem like I cannot reproduce the error. While I prefer a small delay, since you are correct (in this case we are not making an actual servery query) using a 0ms delay is a work around I can use until this is addressed.

    However, I'm getting the following error below (more frequently). I am assuming this is fixed in 3.0.3; since it seems to be the same error (even though it happens a little differently) to the one I reported here:

    http://www.sencha.com/forum/showthre...306#post887306
    EXTGWT-2438


    Stack Trace
    ---------------

    (Error): Can't move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus.




    Exception: com.google.gwt.core.client.JavaScriptException


    Stack Trace:


    com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:248)
    com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)
    com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:561)
    com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:269)
    com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)
    com.google.gwt.core.client.impl.Impl.apply(Impl.java)
    com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213)
    sun.reflect.GeneratedMethodAccessor391.invoke(Unknown Source)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    java.lang.reflect.Method.invoke(Method.java:611)
    com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
    com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
    com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
    com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:292)
    com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:546)
    com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:363)
    java.lang.Thread.run(Thread.java:736)

    And because we display errors for exceptions that are not caught, this is getting in the way.

    GWT.setUncaughtExceptionHandler(
    new GWT.UncaughtExceptionHandler() {
    public void onUncaughtException(Throwable e) {
    Log.fatal("unexpected exception", e);
    // popup dialog with exception.
    }
    }
    );

  4. #4
    Ext GWT Premium Member
    Join Date
    Dec 2011
    Location
    Earth
    Posts
    243
    Vote Rating
    1
    nbuesing is on a distinguished road

      0  

    Default


    I created a grid with 4 columns (and two editors in each row) and held down the tab key.

    I have setQueryDelay(0) on both column editors.

    I was still able to get the combo box to appear at coordinate 0,0. So, this workaround looks to be an ok temporary solution (since I had to really try to get it to reoccur), but obviously, a fix is still needed.

    Thanks again for your help.

  5. #5
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,731
    Vote Rating
    90
    Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light

      0  

    Default


    Thanks for your feedback - I do indeed suspect that the issue you pointed out is unrelated, and that it has been fixed (fix is approximately: try {focus()} catch (Exception e) {/*ie is stupid*/}). If you are able to test your case with a nightly build, I think you'll find that this issue is gone, and that the query delay also helps to mitigate the issue in this thread.

    As mentioned, I'll update this thread when a fix is in SVN - it should be in the nightly build within 24 hours of that update.

  6. #6
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,731
    Vote Rating
    90
    Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light

      0  

    Default


    This issue has been marked as fixed internally, with a commit in SVN with the needed changes. The change is available in the nightly builds, and can be seen on our nightly build server. It will be made available in the next release.

    There is a possibly related issue we are still chasing - in Chrome, in the Cell Grid example, it is still possible to reproduce something like this bug, but only after clearing out cells in a specific order. This was the only issue reported internally that may be related to this fix, and I'll comment here when this has been resolved.

Thread Participants: 1

Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..."