Image content renders as black areas in external document views (serverType EXTERNAL) when “Optimize Page Interactions” is enabled
Title: Image content renders as black areas in external document views (serverType EXTERNAL) when “Optimize Page Interactions” is enabled
Product / version: Adobe Acrobat (Acrobat Studio for Teams), Continuous Release 2026.003.22110, 64-bit, Windows 11
Summary:
Our Acrobat plug-in displays documents inside its own window using the Acrobat SDK’s external document mode. When “Optimize Page Interactions” is enabled, parts of the page, especially image content, are drawn as solid black or grey areas inside the external view. With the option disabled, the same documents render correctly, as they have in all previous versions.
How the document is opened:
AVDocOpenFromFileWithParams with:
useServerType = true, serverType = "EXTERNAL"
serverCreationData → ExternalDocServerCreationDataRec with platformWindow = the HWND of a native child window in our plug-in UI
useViewType = true, viewType = "AVDocView", useReadOnly = true, readOnly = true
useViewDef = true (fit width, page 0)
Steps to reproduce:
Enable Optimize Page Interactions. On our test machine it’s only available when HKCU\Software\Adobe\Adobe Acrobat\DC\IPMExperiments\cDirectManipulationIPMConsumer\iVariant = 2.
Open a PDF that contains raster images in an external document view as described above.
Parts of the page that contain image content render black or grey. The shape follows the image content, so it isn’t a rectangle over the view.
Expected: The page renders the same as in a normal Acrobat document window.
Actual: Image regions render as black or grey areas. Forcing a repaint (RedrawWindow on the host and child windows, AVPageViewDrawNow) doesn’t fix it. Disabling WPF hardware acceleration in our UI doesn’t change it either.
Workaround: Setting HKLM\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown\bDirectManipulationIPMConsumer = 1 turns the feature off, and rendering is correct again.
Request: Please confirm whether external document views are supported with the new rendering. If they aren’t, please tell us whether a fix is planned or whether there’s a supported way for a plug-in to opt its external views out of the new rendering.