Yup saw that - should resolve the issue with the scroller getting out of whack. Probably will make scrolling expensive, but alteast usable. but still has the issue of the text showing through stuff (like dropdowns and popups and such). So basically we need to evaulate objects underneath these popups and hide them if they are text inputs and show them back when the popups are closed. Yuck. Any better ideas?
On Sun, Sep 29, 2013 at 11:20 PM, jude <flexcapaci...@gmail.com> wrote: > Not so much gracefully but this might help, > > http://stackoverflow.com/questions/14412301/flex-textarea-and-textinput-on-mobile-not-positioning-correctly > . > > > > > > On Sun, Sep 29, 2013 at 9:28 PM, Flexicious.com <flexici...@gmail.com > >wrote: > > > This may not be a Flex/Apache issue, but just wanted to see if anyone has > > been successful with text on Air mobile. > > > > The issue basically revolves around the native text input. It is rendered > > on top of the display list, and it does not scroll within its parent > > scroller. So dropdowns and such that render on top of it do not hide it, > > and if the user scrolls the text stay in place. There are some more > > details here: > > > > > > > http://stackoverflow.com/questions/15840504/what-options-are-available-for-handling-text-input-on-android-using-adobe-air > > https://bugbase.adobe.com/index.cfm?event=bug&id=3302441 > > > > Some have suggested using the older spark.mobile.TextInputSkin but with > > Air 3.8 and iOS7 on iPad , the workaround suggested is not an option. It > > seems to be even more problematic, as you type it selects what you have > > typed so you cannot effectively type anything without erasing what was > > there. > > > > A comment from an Adobe person here suggests the issue with the older > > TextinpustSkin is a Flex SDK issue. > > https://bugbase.adobe.com/index.cfm?event=bug&id=3292370 > > > > Has anyone run into this, if so, been able to handle it gracefully? > > >
