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

Rajeev  commented on WICKET-3093:
---------------------------------

Thanks Attila for the suggestion. I verified in my real app and doctype is 
properly define as html.

Below are the things that are not working in real app:
1. When I type text, focus moves back to the beginning of text field.
2. When I click suggestion, it does not update in text field.

I have implemented onchange behavour on AjaxFormComponentUpdatingBehavior. Same 
thing is working fine now in test project without any issues.

Also, in actual code, it is requesting focus on searchbox when nothing is 
entered in textbox(textbox is blank). So it focus should not move the beginning 
of the field when I have already added some text in it.


> Self-updating AutoCompleteTextField moves focus to start of field in IE only
> ----------------------------------------------------------------------------
>
>                 Key: WICKET-3093
>                 URL: https://issues.apache.org/jira/browse/WICKET-3093
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.4.12
>            Reporter: Alex Grant
>            Assignee: Martin Grigorov
>            Priority: Minor
>         Attachments: WICKET-3093-autocomplete.zip, WicketTestProject.zip
>
>
> I have an AutoCompleteTextField that has a AjaxFormSubmitBehavior("onchange") 
> attached so that we can canonicalise the value (eg correct the case) 
> automatically. In IE only, when you pause long enough to trigger the 
> AjaxFormSubmitBehavior, the cursor moves to the start of the text field, so 
> if you type "123" slowly you may be "312".
> This is only an issue in IE as it is caused by WICKET-2279 - if I remove the 
> javascript added for that bug the problem goes away.
> The problem can also be solved by changing AjaxFormSubmitBehavior("onchange") 
> to AjaxFormSubmitBehavior("onblur"), but I still consider it a bug given it 
> only occurs in IE - Firefox and Chrome behave correctly no matter what you do.
> Also, since the javascript added in WICKET-2279 starts with the comment "// 
> hack for a focus issue in IE, WICKET-2279" I figured you'd like to know about 
> any quirky behaviour it causes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to