This is not an answer to the question, but might help others in the same circumstances.
I suspect it is because the childViewModel property does not raise the PropertyChanged event. When the binding is evaluated, it is possible that this property is null (in which case the DataContext will just fall back to the parent's one). When the childViewModel is instantiated later, no PropertyChanged event is raised, and the binding is never informed that there is now a DataContext.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.