0 Replies Latest reply on Jun 26, 2009 7:50 AM by Peter Farland

    [svn:fx-trunk] 8303: This change tries to support legacy usages of StyleManager. setStyleDeclaration() while keeping the new "subject based" internal index of style declarations in sync with selectors.

    Peter Farland Level 3

      Revision: 8303

      Author:   pfarland@adobe.com

      Date:     2009-06-26 07:50:46 -0700 (Fri, 26 Jun 2009)

       

      Log Message:

      ***********

      This change tries to support legacy usages of StyleManager.setStyleDeclaration() while keeping the new "subject based" internal index of style declarations in sync with selectors. We no longer support the invalid usage of constructing a CSSStyleDeclaration with one selector but re-registering it with StyleManager.setStyleDeclaration with another selector.

       

      QE: Yes, look out for test cases that incorrectly create a CSSStyleDeclaration with a selector AND also use StyleManager.setStyleDeclaration(). I saw one invalid usage in the mustella test file: tests/Managers/StyleManager/AdvancedCSS/mixedSelectors/AdvancedCSS_MixedSelectors, specifically the "CSSStyleDeclaration_CSSSelectorKind_Type_method" test case.

       

      Doc: Yes, please remove any examples that showed a CSSStyleDeclaration being constructed with a "name" as that is incorrect. You only construct these instances with a selector, or nothing.

       

      Reviewer: Glenn

      Checkintests: Pass

      Bugs:

      SDK-21714 - Dynamically created styles are ignored by spark components

       

      Ticket Links:

      ************

          http://bugs.adobe.com/jira/browse/SDK-21714

       

      Modified Paths:

      **************

          flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/StyleManagerImpl.as