You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Colin Childs (JIRA)" <ji...@apache.org> on 2013/11/25 19:56:36 UTC

[jira] [Comment Edited] (FLEX-33928) On android, numeric software does not work well

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

Colin Childs edited comment on FLEX-33928 at 11/25/13 6:55 PM:
---------------------------------------------------------------

I was finally able to nail down a solid reproducible test case for this bug. Tested on Samsung Galaxy S1 and Galaxy Tab 7.0  2. When transitioning from a TextArea to a numeric TextInput, the keyboard stays as the default keyboard instead of the numeric one, and although the TextInput appears focused, it has no blinking caret and typing does nothing. With proxy debugging on, it looks like it is NOT showing the proxy at this point. Sometimes on slower devices, you can actually see the numeric keyboard come up, then switch to the default one instead. It looks I could only get this to happen when the TextArea is on the bottom of the screen, below the area where the softkeyboard will show. To reproduce, simply create a new Flex mobile project and place a TextArea inside a Scroller at the bottom of the screen and put a numeric TextInput above that. You may need 50+ px of padding between the two components. Tap on the TextArea to bring up the softkeyboard, then tap on the numeric TextInput to bring up the numeric keyboard. At this point, the numeric input will have a default keyboard instead. This may have something to do with the fact that the screen pans up to show the TextArea, then pans back down a little after the TextInput gains focus. Note that you will probably need to set the keyboard behavior to "pan" in order to get the screen to raise up high enough to show the numeric TextInput.

My test case:

{code}
<s:Scroller width="100%" height="100%">
  <s:VGroup gap="50" horizontalAlign="center" verticalAlign="bottom"
    <s:TextInput width="90%" softKeyboardType="number" />
    <s:TextArea width="90%"/>
  </s:VGroup>
</s:Scroller>
{code}

Additionally, I am not sure, but I believe there may be an issue with Scroller panning behavior when softKeyboardBehavior is set to "none". With a non-StageText skin, the Scroller will pan up to show the field even when softKeyboardBehavior is set to "none" instead of "pan". With ScrollableStageText, it remains hidden behind the softkeyboard.


was (Author: cchilds):
I logged this in 33166 but realized it would probably be better here:

I was finally able to nail down a solid reproducible test case for this bug. Tested on Samsung Galaxy S1 and Galaxy Tab 7.0  2. When transitioning from a TextArea to a numeric TextInput, the keyboard stays as the default keyboard instead of the numeric one, and although the TextInput appears focused, it has no blinking carat and typing does nothing. With proxy debugging on, it looks like it is NOT showing the proxy at this point. Sometimes on slower devices, you can actually see the numeric keyboard come up, then switch to the default one instead. It looks I could only get this to happen when the TextArea is on the bottom of the screen, below the area where the softkeyboard will show. To reproduce, simply create a new Flex mobile project and place a TextArea inside a Scroller at the bottom of the screen and put a numeric TextInput above that. You may need 50+ px of padding between the two components. Tap on the TextArea to bring up the softkeyboard, then tap on the numeric TextInput to bring up the numeric keyboard. At this point, the numeric input will have a default keyboard instead. This may have something to do with the fact that the screen pans up to show the TextArea, then pans back down a little after the TextInput gains focus. Note that you will probably need to set the keyboard behavior to "pan" in order to get the screen to raise up high enough to show the numeric TextInput.

My test case:

{code}
<s:Scroller width="100%" height="100%">
  <s:VGroup gap="50" horizontalAlign="center" verticalAlign="bottom"
    <s:TextInput width="90%" softKeyboardType="number" />
    <s:TextArea width="90%"/>
  </s:VGroup>
</s:Scroller>
{code}

Additionally, I am not sure, but I believe there may be an issue with Scroller panning behavior when softKeyboardBehavior is set to "none". With a non-StageText skin, the Scroller will pan up to show the field even when softKeyboardBehavior is set to "none" instead of "pan". With ScrollableStageText, it remains hidden behind the softkeyboard.

> On android, numeric software does not work well
> -----------------------------------------------
>
>                 Key: FLEX-33928
>                 URL: https://issues.apache.org/jira/browse/FLEX-33928
>             Project: Apache Flex
>          Issue Type: Sub-task
>          Components: .Unspecified - Mobile, Mobile: Text
>            Reporter: Maurice Amsellem
>            Priority: Minor
>             Fix For: Apache Flex 4.8 (parity release), Apache Flex 4.9.0
>
>
> (Collins)



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