[
https://issues.apache.org/jira/browse/FLEX-33166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Childs updated FLEX-33166:
--------------------------------
Comment: was deleted
(was: I was finally able to nail down a solid reproducible test case for one of
my recent bugs logged about Android. 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.)
> Mobile TextInput with native StageTextInput cannot be included in scrollable
> forms
> -----------------------------------------------------------------------------------
>
> Key: FLEX-33166
> URL: https://issues.apache.org/jira/browse/FLEX-33166
> Project: Apache Flex
> Issue Type: Bug
> Components: .Unspecified - Mobile, Mobile: Text
> Affects Versions: Adobe Flex SDK 4.6 (Release)
> Environment: All IOS
> Reporter: Dan Murray
> Assignee: Maurice Amsellem
> Labels: features, mobileTextInput
> Fix For: Apache Flex 4.8 (parity release), Apache Flex 4.9.0
>
> Attachments: MultiFocusBug.PNG, TextInputTest.zip
>
> Original Estimate: 612h
> Time Spent: 96h
> Remaining Estimate: 48h
>
> We should be able to configure a text field which only accepts numerical
> input to call up the numeric pad. However, the skinclasses for the textfield
> that can call up the number pad will not scroll--If you try to use the
> skinclass that can call the softkey number pad in a scrollable container, the
> textfield scrolls away from its text.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
