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

Maurice Amsellem edited comment on FLEX-33729 at 11/19/13 4:08 PM:
-------------------------------------------------------------------

fix is not needed, as the default skin now supports being embedded in a 
scroller.
See: https://issues.apache.org/jira/browse/FLEX-33166


was (Author: mamsellem):
fix is not needed, as the default skin now supports being embedded in a 
scroller.

> Softkey-board related features does not works on ios for TextInput if 
> MobileSkin is used.
> -----------------------------------------------------------------------------------------
>
>                 Key: FLEX-33729
>                 URL: https://issues.apache.org/jira/browse/FLEX-33729
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: TextInput
>    Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.10.0
>         Environment: iPhone All
>            Reporter: Shardul Singh Bartwal
>              Labels: mobileTextInput
>             Fix For: Apache Flex 4.12.0
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> Problem Description: Softkey-board related features like 
> autoCapitalize,softKeyboardType does not works on ios for TextInput if 
> MobileSkin is used with the TextInput.
> Steps to Reproduce: With any ios based air application the textiput as below:-
> <s:TextInput skinClass="spark.skins.mobile.supportClasses.MobileSkin" 
> autoCapitalize="sentence" softKeyboardType="number"/> 
> When one will touch on this Textinput on ios softkeyboard type will not open 
> as number and also autoCapitalize will not work.
> Actual Result: This will not show the softkeyboardtype to number and also 
> will not do autoCapitalize because we have used MobileSkin.
> Expected Result: SoftkeyboardType should be number when it open and also 
> autoCapitalize should work as it works when we don't use MobileSkin.
> Issue is reported one year back to adobe but nothing from their end:-
> https://bugbase.adobe.com/index.cfm?event=bug&id=3292370



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to