History transition executable content - when is it executed?

While implementing the SCXML Algorithm, I noticed the handling/processing of 
executable content of a History transition isn't taken care of yet.
Neither in the Algorithm nor in wording (when) in the specification.

The addDescendantStatesToEnter procedure dereferences History states, so these 
History states correctly don't end up in the statesToEnter, but then neither 
will their possible transition executable content be processed.

And as important: when should History transition executable content be processed?

It seems like an obvious choice that it should happen after the History parent 
state onentry and before any History default targets onentry execution.

Any opinions?

At any rate, I think this needs to be clarified in the specification, and also 
integrated in the Algorithm.

Kind regards,
Ate