[
https://issues.apache.org/jira/browse/FLEX-33911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maurice Amsellem updated FLEX-33911:
------------------------------------
Description:
There are two use cases for partial occlusions:
1) The TextInput is embedded in a scrollable form, and is scrolled so that only
part of TextInput is visible
2) The TextInput partly overlap with anothe floating UI (palette, etc.)
In both cases, when the TI is edited, it will display completely, thus
overlapping the UI around.
Note1: when the TI is not edited, it's correctly clipped
Note2: this is not to be confused with TI that are partly off-screen, which are
handled correctly.
was:
There are two use cases for partial occlusions:
1) The TextInput
> Partially Occluded mobile TextInput/TextArea will overlap other UI when edited
> ------------------------------------------------------------------------------
>
> Key: FLEX-33911
> URL: https://issues.apache.org/jira/browse/FLEX-33911
> Project: Apache Flex
> Issue Type: Bug
> Components: Mobile: Text, Spark: TextInput
> Reporter: Maurice Amsellem
> Assignee: Maurice Amsellem
>
> There are two use cases for partial occlusions:
> 1) The TextInput is embedded in a scrollable form, and is scrolled so that
> only part of TextInput is visible
> 2) The TextInput partly overlap with anothe floating UI (palette, etc.)
> In both cases, when the TI is edited, it will display completely, thus
> overlapping the UI around.
> Note1: when the TI is not edited, it's correctly clipped
> Note2: this is not to be confused with TI that are partly off-screen, which
> are handled correctly.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
