Hi Chris,

Thanks for the video. I am able to reproduce the issue now. The steps you provided previously don't match up to what you are actually doing to reproduce the issue as shown in the video, so that's probably why I could not get it to happen before.

ChrisBrooks said:

If you run the sample, then scroll to the bottom where the UCAuthentication controls are, then activate them, then scroll up and click on one of the radio buttons, then scroll back down and click on the UCAuthentication again, sometime the issue will happen.  I will continue to work at the exact way to duplicate the behavior, and when I figure it out, post how to do it here.

Anyway, I still can't reproduce it every time, but there is definately something weird going on in your sample application.

I noticed that when I drag the scroll thumb all the way to the bottom, the last row lines up flush with the bottom of the grid. But as soon as I release the mouse, the grid jumps and everything shifts up and there's a gap between the last row and the bottom of the grid.

This shift is about the same height as the controls shift sometimes when the problem happens. So I think they are related.

My guess is that both issues have the same cause and that it's your CreationFilter. Inside your CustomCreationFilter class, you are changing the Height property on the grid row. This is a very bad idea. The UIElements in the grid are created an positioned based on the properties that the grid returns. You should never set properties on the 'real' grid objects inside a CreationFilter.

It looks like you are simply trying to determine the correct height for the row, but you cannot do this inside a CreationFilter.

If I leave the CreationFilter on and simply remove the line of code that sets the Row.Height, then once again, the problem with the scrollbar goes away and I cannot reproduce the problem you are having, either.

So I'm pretty sure that the problem here is caused by your CreationFilter.

I am attaching the video file here.

Mike,

Our QA was able to create a video of the problem, but cannot compress it down to less than 3 Megs. How would i be able to get this to you?

-Chris