[
https://issues.apache.org/jira/browse/FLEX-33742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-33742:
---------------------------------
Labels: easytest patch (was: )
> CalloutButtons inside another CalloutButton or Callout opened contents
> closeDropDown calls close the parent callout content
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: FLEX-33742
> URL: https://issues.apache.org/jira/browse/FLEX-33742
> Project: Apache Flex
> Issue Type: Bug
> Components: Mobile: Callout / CalloutButton
> Affects Versions: Apache Flex 4.10.0
> Environment: Windows
> Reporter: Carlos Velasco Blanco
> Priority: Minor
> Labels: easytest, patch
> Attachments: CalloutButtonIssueAndWorkaround.fxp
>
>
> When using a callout button inside the callout content of a different callout
> button I am having an undesired effect.
> Calling the dropdown method of the child callout button (the one placed at
> the callout content) is closing its callout content (as desired) but also
> closing the parents callout content.
> CalloutButton instances are to be closed using the closeDropDown() method
> which is causing the problem. Calling it for one instance is closing all
> instances. I think it was programmed that way thinking there would never be 2
> CalloutButton instances opened at a time, but It really happens when you use
> CalloutButtons inside the contents that are displayed when an instance of
> CalloutButton is opened.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
