A few workarounds have been identified and used to resolve a number of these issues. These workarounds and are detailed in this TechNote for consideration.
Thorough client-server testing of these workarounds is recommended to assess the final application behavior in advance of any deployment into a production environment. For additional inquiry, please contact Adobe support through your normal channels or visit www.adobe.com/support/.
In some cases these issues are due to a new rendering method called direct rendering (AGM), and disabling AGM has resolved a number of these issues.
It is recommended that you test one or more of the following workarounds to determine whether disabling AGM resolves the issue.
Disable Direct Rendering (AGM) on a per form basis
Using LiveCycle Designer, add the following processing instruction to the template definition to disable direct rendering method on a per form basis:
<?originalXFAVersion http://www.xfa.org/schema/xfa-template/2.1/ LegacyRendering:1?>
Disable Direct Rendering (AGM) on the client environment via the Windows registry
For situations where Acrobat and Reader clients are used under a controlled environment or network, direct rendering (AGM) can also be enabled or disabled by adding a new key and value to the Windows registry.
Disclaimer: The registry contains system-related information that is critical to your computer and applications. Before modifying the registry, be sure to make a backup copy of it. Adobe doesn't provide support for problems that arise from improperly modifying the registry. Adobe strongly recommends that you have experience editing system files before you modify the registry. For information on the Windows Registry Editor, see Windows documentation or contact Microsoft Technical Support.
To disable AGM, edit the Windows registry as follows:
