We are seeing an issue with the DateTimeEditBox (DTEB). The scenario is pretty simple (but not so simple to explain, but I'll try).
We have a DTEB bound to a Nullable<DateTime> property in our ViewModel. We are seeing our issue when the Nullable<DateTime> property transitions from a valid datetime value to a null value. It appears that in this scenario, for whatever reason the DTEB receives logical focus (only for a brief moment), only to hand focus off to another element in the tree. There is a very subtle side affect to this brief acquisition of focus. The moment the DTEB gets focus it raises the FrameworkElement.RequestBringIntoView event. At this point, our containing scroll viewer will attempt to honor that request shifting the view to the DTEB that raised the event. This results the screen scrolling to the location of the DTEB confusing our users.
Note that the control only behaves this way when transition between null and a valid value. It does not do this when the view model property is change between 2 valid datetime values.
Any insight would be great!