flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stepan Hilbert (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
Date Wed, 30 Jan 2013 02:37:12 GMT

     [ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stepan Hilbert updated FLEX-33372:
----------------------------------

    Component/s: Spark: RichEditableText
    
> Windows 8 on-screen touch keyboard not displaying
> -------------------------------------------------
>
>                 Key: FLEX-33372
>                 URL: https://issues.apache.org/jira/browse/FLEX-33372
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: RichEditableText, Spark: TextArea, Spark: TextInput
>    Affects Versions: Adobe Flex SDK 4.6 (Release)
>         Environment: Windows 8 Metro
> Internet Explorer (IE) 10.0.1
> Flash Player 11,3,378,5
>            Reporter: Stepan Hilbert
>
> On-screen touch keyboard is not being displayed for spark text input components. It should
get displayed just as it gets displayed for TextField based components.
> Additionally, it would be desirable to control the keyboard using:
> - needsSoftKeyboard property
> - requestSoftKeyboard() function
> These currently have no effect.
> Steps to reproduce:
> 1. Create a Flex application that features s:TextInput and mx:TextInput
> 2. Open this application in the Metro Internet Explorer on a touch-enabled Windows 8
PC/Tablet. You might need to edit the DebugDomain variable (see http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx)
> 3. Tap the mx:TextInput - on-screen keyboard shows
> 4. Tap the s:TextInput - on-screen keyboard doesn't show
> Note:
> This bug has been discussed on the web
> (i.e. here: http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html)
> but no resolution has been reached, so that is why I'm logging this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message