Embedded children displayed property should be set to true once the parent has been displayed. pipeline._getTask should store new task objects in this.tasks.
Dependencies and sections are now only referred as children in specs; children that are dependencies must specify 'block' as true. Children tasks can be defined statically in the configuration or dynamically during runtime; this makes two things possible which weren't before: sections can be defined during runtime, including within non-section tasks, and children dependencies can be defined in the static configuration. The order of Pipeline flushing to the client is now guaranteed to occur in the same order that initiated the flushing; this fixed a bug where the second flush was executed before the first flush because the first flush was waiting on the frame to finish rendering, resuling in the frame appearing twice. Updated tests and sample application.
Renabled tests that were commented out.
Added comments, renamed block to blockParent, renamed default to autoPush. Making sure that sections with flush or display rules are not embedded in their parents to ensure that their rules are honored.
Enabling the disabled tests.
Removed references to sections and dependencies, instead there are just childrenTasks. Checking user errors regarding blocking tasks with flush/display rules, and pushing a blocking child after a parent has been pushed without know that it has a blocking child. Making sure that flushed tasks have a parent in displayTargets otherwise it should listen to all tasks' afterDisplay events to check for a stub. Fixed Task.toString method, which was not embeding children when js is disabled.
Merge pull request #19 from aljimenez/master

Sections and dependencies referred to as children