wicket-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Attila Király (JIRA) <j...@apache.org>
Subject [jira] Commented: (WICKET-3093) Self-updating AutoCompleteTextField moves focus to start of field in IE only
Date Wed, 09 Mar 2011 11:38:59 GMT

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

Attila Király commented on WICKET-3093:

Guess you are setting the "X-UA-Compatible" as meta header in the html head section. In that
case note this:
"The X-UA-Compatible header is not case sensitive; however, it must appear in the header of
the webpage (the HEAD section) before all other elements except for the title element and
other meta elements."
So it must be at the start of the head section. Or you can send it as a response header.

> 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

View raw message