Default values of a component should be set automatically before the includeIn action

The way includeIn is working with transitions seems to be having an unwanted behaviour.
Consider the following:

<s:Panel id="loginView"
title="Test"
width="300"
height="200"
includeIn="loginState"
horizontalCenter="0"
verticalCenter="15"
verticalCenter.loginState="0"
alpha="0"
alpha.loginState="1"/>

If I have a transition to loginState, the transition uses 0,0 as the initial "x" and "y" values. Shouldn't they be the ones defined by the default horizontalCenter/verticalCenter value?

When the AddChild runs due to the includeIn, then x and y are changed to the values defined by the horizontalCenter and verticalCenter. If I have a transition with a Move Effect,we will see the panel moving from the point 0,0 to the center of the screen; When, according to the code (default verticalCenter=15, loginState verticalCenter =0), we would expect to see panel going from it's default value's positions to it's loginState value's positions.

After the first time the includeIn operation is executed everything works as expected. But the first time it simply seems to have an erratic behavior.

See the example running here:

http://www.webfuel.pt/jsaleiro/flex/transitions/AddChildTest.html

Press the top left corner button several times. Notice that on the first click the panel has a weird transition.
Source is available here: http://www.webfuel.pt/jsaleiro/flex/transitions/srcview/source/AddChildTest.mxml.html

Shouldn't the default values be applied before the includeIn operation?

My build version 13363.

Added to JIRA by recommendation of Corey Lucier.