[FLEX-16826] Investigate styleChanged propagation methodology for Group, Skin, and FxContainer.

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Later
• Affects Version/s: Adobe Flex SDK Previous
• Component/s: Spark: Group, Spark: SkinnableComponent, Spark: SkinnableContainer
• Environment: Affected OS(s): All OS Platforms; Affected OS(s): All OS Platforms; Language Found: English
• Assignee: Adobe JIRA
• Reporter: Adobe JIRA
• Created: 08/Dec/08 11:27
• Updated: 15/Apr/11 15:23
• Resolved: 10/Apr/09 17:57

Description

There are two methods, notifyStyleChangeInChildren and regenerateStyleCache that Container overrides and treats differently than UIComponent. We need to research the motivation behind the logic and ensure Group, Skin, and FxContainer (our new Gumbo containers) are doing the right thing with regards to style change propagation and style cache regeneration.

Specifically:

notifyStyleChangeInChildren:

1. Why does Container propagate style change to chrome children always (even when recursive is false).
2. Why does Container defer change notification of content children (until property validation) when recursive is true.

regenerateStyleCache:

1. Why does Container skip UIComponent children when recursive is false, but not IUITextField children.