0 Replies Latest reply on Aug 7, 2009 3:16 PM by Jason Szeto

    [svn:fx-trunk] 9182: PopUpAnchor bug fixes

    Jason Szeto Level 3

      Revision: 9182

      Author:   jszeto@adobe.com

      Date:     2009-08-07 15:16:18 -0700 (Fri, 07 Aug 2009)


      Log Message:


      PopUpAnchor bug fixes


      http://bugs.adobe.com/jira/browse/SDK-22425 - Opening a DropDownList that is in a child application from a different domain from the parent causes a RTE


      PopUpAnchor references the stage for some fullScreenMode logic. The fix is to put a try/catch around this code. If we are in a subapplication, accessing the stage?\226?\128?\153s displayState property is a security violation. It is not a critical calculation, so it is alright if it isn?\226?\128?\153t run.


      Fixing the RTE exposed a different bug involving what transforms to apply to the popUp. The original code was applying the concatenatedMatrix of the PopUpAnchor to the popUp. However, when the PopUpAnchor is in a sub application in a different domain, then the popUp is parented by a systemManager that is a child of the main application. This resulted in concatenated transforms applied to the sub application getting applied twice. The fix is to get the concatenated transform from the popUp?\226?\128?\153s parent to the PopUpAnchor. I get this transform by taking the concatenated transform and subtracting out the popUp parent?\226?\128?\153s concatenated transform.


      QE notes: Add tests for subapplication/module use cases

      Doc notes: None

      Bugs: SDK-22425

      Reviewer: Alex

      Tests run: DropDownList, PopUpAnchor

      Is noteworthy for integration: No


      Ticket Links:





      Modified Paths: