[ 
https://issues.apache.org/jira/browse/WICKET-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899154#comment-17899154
 ] 

ASF GitHub Bot commented on WICKET-7132:
----------------------------------------

strido opened a new pull request, #1039:
URL: https://github.com/apache/wicket/pull/1039

   When using tab to leave an auto complete field without anything selected the 
editing does not work immediately if returning to the field. One will need to 
type at least one character before the autocomplete will trigger an opening of 
the dropdown.
   




> Tabbing from AutoComplete fields and back doesn't work as expected
> ------------------------------------------------------------------
>
>                 Key: WICKET-7132
>                 URL: https://issues.apache.org/jira/browse/WICKET-7132
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>            Reporter: Erik Strid
>            Priority: Minor
>         Attachments: myproject-tab-glitch.zip
>
>
> When using tab to leave an auto complete field without anything selected the 
> editing does not work immediately if returning to the field. One will need to 
> type at least one character before the autocomplete will trigger an opening 
> of the dropdown.
> I have attached a quick start that reproduces this. 
>  # Type something in the (first) text field to open the dropdown.
>  # Press {{tab}} to move to the next component.
>  # Press {{{}shift{}}}+{{{}tab{}}} to return to the auto complete field.
>  # The first edit will not result in the list being re-opened, but the second 
> and subsequent edits will.
> The problem seems to be relate to how {{isTriggeredChange}} and 
> {{triggerChangeOnHide}} is updated specially in the blur event listener.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to