[
https://issues.apache.org/jira/browse/WICKET-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651503#action_12651503
]
Dipu C Seminlal commented on WICKET-1960:
-----------------------------------------
that's exactly the reason why I say reverting back to
container.style.zIndex=(Number(index)!=Number.NaN?Number(index)+1:index);
on the trunk is not quite right
if index = 'auto' (or any non number )
the expression Number(index)!=Number.NaN?Number(index)+1:index
will result in Number(index)+1
if index = 100 (a number )
then also expression Number(index)!=Number.NaN?Number(index)+1:index
will result in Number(index)+1
and I can't think of a condition in which it will result in index and that
looks wrong to me
Regards
Dipu
> AutoCompleteTextField - gives a type mismatch error on IE - version
> wicket-1.4-rc1
> ----------------------------------------------------------------------------------
>
> Key: WICKET-1960
> URL: https://issues.apache.org/jira/browse/WICKET-1960
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.4-RC1
> Reporter: Dipu C Seminlal
> Fix For: 1.4-RC1
>
> Attachments: wicket-autocomplete-patch.txt
>
>
> wicket-autocomplete.js
> function function showAutoComplete()
> line 291 container.style.zIndex=(!isNaN(Number(index))?Number(index)+1:index);
> looks like IE doesn't like big i in zIndex, IE seem to be be happy with
> zindex
> not sure if that's the correct way to resolve the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
