The issue is caused by memory optimization that requires loading page content only for the visible pages. In order to fix the issue and still benefit from the memory optimization, we are introducing setter in FixedDocumentPresenterBase VisiblePages property. Now this property needs to be set each time the visible pages are changing in custom presenter implementation. Setting VisiblePages ensures that all visible pages content will be loaded correctly.
Hi, The issue is fixed and will be live in our next LIB release. It will be included in our upcoming 2016 R3 release as well. Regards, Aylin, Telerik by Progress