Feature differentiation between HTML5 forms and PDF forms
The following table specifies the feature support provided for HTML5 forms and PDF forms:
|Barcodes||Not available at the user interface level.||Supported|
|Signature field||Digital Signatures are not supported but a new Scribble Signature field is added for paper like signatures. One can scribble their signature on the form using the Scribble Signature field. The signature is saved on the form as an image. You can save geolocation information in the Scribble Signature field.||Signature field available for Digital Signatures .|
|Images||The Data URI scheme is used to display images. All the modern versions of browsers support this scheme but there are differences in the range of image formats that each browser supports.||The .gif, .png, .jpeg, .bmp, and .tiff formats are supported.|
An HTML5 form is divided into panels and boxes to give it an appearance similar to PDF forms. The size of the page is calculated dynamically. If all the contents of a page in an HTML5 form are deleted or marked hidden, then the blank page is hidden and an empty space (blank space) is not displayed between pages above and beneath the blank page.
If data-merge or scripts add content to a page, then the length of the page expands to accommodate the newly added content. No new pages are added to the form to accommodate the newly added content.
Note: When the all the contents of a page in an HTML5 form are deleted or marked hidden, the blank page (blank space) remains visible between 1st and 2nd page but not between any other pages.
|Pagination in PDF depends on data content merged or user content and page count is increased/reduced based on it.|
|Headers/Footers||Supported. As HTML5 mobile forms do not support page breaks, headers and footers appear only once. You can, however, set them up in the layout to appear at multiple places in the mobile forms preview.||Supported.|
|Custom Widgets||One can customize widgets to enhance the user experience on mobile devices.||All widgets are locked down and no custom widget can be plugged.|
|XFA Script API||Supports the most commonly used XFA script constructs. For details list of supported constructs, see scripting support .||Supports all XFA script constructs.|
|Acrobat Script APIs||HTML5 forms support most commonly used APIs. For details, see scripting support .||If the PDF file is opened inside Acrobat or Reader, it also supports all the script APIs that Acrobat provides.|
|Support for right-to-left languages||Supported||Supported|
Follow the best practices to enable a form template for HTML5 renditions and ensure that the behavior and appearance of HTML5 forms and XFA-based PDF is consistent. For detailed list of best practices, see Best practices to design an HTML5 form.