[
https://issues.apache.org/jira/browse/FLEX-24623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848540#comment-13848540
]
Alex Harui commented on FLEX-24623:
-----------------------------------
Even if you increase the access to a method, you will still break third party
code if anyone wrote an override for that method. That's just an unfortunate
risk when changing method signatures and you have to weigh the risk that
someone did this and can't or won't change their code.
For mx_internal, we've said many times that these are undocumented and could
change at any time, so unless you think some major library of code is using it,
feel free to make it official. But keep in mind, everything that you change
from private or mx_internal to protected or public is an API we have to carry
with us for backward compatibility from that day on, I would be selective. It
also makes the documentation harder to wade through.
> Remove private declarations in PopUpAnchor
> ------------------------------------------
>
> Key: FLEX-24623
> URL: https://issues.apache.org/jira/browse/FLEX-24623
> Project: Apache Flex
> Issue Type: Improvement
> Components: Spark: PopUpAnchor
> Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Other (specify version)
> Language Found: English
> Reporter: Adobe JIRA
> Assignee: Maurice Amsellem
> Attachments: Fix_for_FLEX-24623.patch
>
>
> I'm trying to entend PopUpAnchor to add the ability to create modal popups
> with it (see https://bugs.adobe.com/jira/browse/SDK-27136).
> Due to the plethora of private methods and variables I am unable to do this,
> and have had to duplicate the entire class (which is still very common when
> trying to extend or change the functionality of Adobes components).
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
