Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
Apache Flex 4.10.0
-
None
-
Windows
Description
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.
Attachments
Attachments
Issue Links
- is related to
-
FLEX-35124 RTE 1009 in DropDownController.systemManager_mouseDownHandler() when inside a PopUpAnchor and other item is removed on click
- Resolved
I have checked the source code, and the bug seems to be in DropDownController.systemManager_mouseDownHandler(), which makes an incorrect assumption.
It assumes that if a mouse down event occurs OUTSIDE of the callout, then the callout should be closed.
This is true, unless the mouse down occurs INSIDE ANOTHER Callout, in which case, it should be ignored.
See code below: