- From: David Junger <tffy@free.fr>
- Date: Tue, 25 Mar 2014 01:23:02 +0100
- To: Voice Public List <www-voice@w3.org>
Since they're restricted much like those in <initial>, I had a look at that, but it appears <initial> transitions "may" have executable content too. I don't see a clear statement about when that should be executed either, and I don't see it in the pseudocode (tell me if I'm wrong, but I'm going to proceed under the assumption that I didn't miss it). Your proposal makes the <history> transition executable content run during the entry phase (between the parent state's onentry blocks and its children's, if I understand correctly). I think that makes sense for those transitions, especially for <initial> and it's OK for <history>. Since you can't trigger both <initial> and <history> for the same parent at the same time, they could safely share the same mechanism for running their executable content. David
Received on Tuesday, 25 March 2014 00:23:32 UTC