If I apply the XamRichTextEditor inside a scrollViewer as done here:
<Grid> <ScrollViewer> <ig:XamRichTextEditor /> </ScrollViewer> </Grid>
then whenever the user types in text and newlines, and reach the end of the editor, then the scrollviewer begins to show but it does not automatically scroll down, so you can see what you are typing. If you did replace the XamRichTextEditor with a normal TextBox this behavior would be as expected. When you reach the visual end of the textbox, and apply newlines it automatically scroll down so you can see these newlines and what you are typing in.
I have attached a sample project that simulates this.
Are there any way to configure the XamRichTextEditor so it gets the same behavior?
Thank you for the post. The behavior you are getting with XamRichTextEditor is because you put it in the ScrollViewer, if you remove the ScrollViewer you will get the expected behavior (same as you are getting with TextBox ).
You don’t need to put XamRichTextEditor in the ScrollViewer as XamRichTextEditor has ScrollViewer internally and it will automatically place a ScrollViewer around its content when its needed.
Let me know if you have any question.
Yes in that simple scenario it will work. But in our scenario we have more than just one field that needs to be included in that scrollviewer. If have added an updated project that proof this. Here we hare included 6 rows, which could be the input form. And we would wrap these into a scrollviewer, so even small screen resolutions can show this form. And in that case i could be great if you could just disable the RTF editor, and let the outer scrollviewer deal with the scrolling. How can this be done? Or do you have any other suggestions on how to handle this.?5710.IGRtfAutoScroll.zip
Thank you for the update.In your sample when I put the whole grid inside the ScrollViewer, I can able to reproduce the issue you described. I logged this behavior into our internal system with id 270540.
I also created a private case ‘’CAS-207930-V8K6K3” and link this development issue so that you will keep getting the update of the issue through this private case.
You can access this private case from your Infragistics account support activity page.