How to Fix Yes and No Reset Confirmation Buttons in Acrobat Mobile
Question details
The user is trying to implement a Yes/No confirmation dialog for a reset form button using JavaScript, but it is not functioning correctly on mobile devices.
- Product
- Adobe Acrobat Reader Mobile
- Device & OS
- Android and iPhone
- Scenario
- Creating interactive PDF forms with JavaScript alert dialogs that prompt users to confirm before clearing or resetting form data.
- Observed behavior
- The Acrobat Reader mobile app only displays a basic OK button for JavaScript alerts and completely ignores conditional Yes, No, or Cancel responses, preventing the reset script from working as intended.
Keep in mind that mobile PDF readers have restricted JavaScript engine support compared to desktop versions. It is highly recommended to test your interactive PDF forms on both desktop and mobile platforms before distributing them.
Remove the Conditional Confirmation for Mobile Compatibility
Since mobile PDF readers cannot process Yes/No JavaScript dialogs, you should modify your PDF form to trigger the reset function directly without a confirmation prompt.
Acrobat Reader for Android and iOS intentionally limits JavaScript alert dialogs to a single 'OK' button. It does not support conditional logic based on different button responses. To ensure your form is usable on mobile devices, you must bypass the prompt.
Transfer your interactive PDF form to a computer and open it using a desktop PDF editor that supports form field editing.
Right-click the 'Reset' button on your form and select 'Properties' from the context menu.
Navigate to the 'Actions' tab, select the 'Run a JavaScript' action, and click 'Edit' to open the script editor.
Delete the conditional code block (such as 'app.alert') that asks for a Yes/No response. Replace the entire script with a direct command: 'this.resetForm();'
Since there is no longer a confirmation prompt, consider moving the Reset button to a less prominent area of the document to prevent accidental taps on mobile screens, then save the document.
Submit a Feature Request to the Product Team
If your workflow absolutely relies on mobile Yes/No confirmations, you can officially request this feature to be added in future updates.
Edit and Manage PDF Forms Seamlessly with WPS Office
If you need to adjust interactive form buttons, remove incompatible mobile scripts, or manage PDF documents efficiently, WPS Office provides a robust and user-friendly desktop PDF editor to customize your files.
- 1. Download WPS Office: Visit the official WPS website, download the free installation package for your computer, and install the software.
- 2. Open the PDF form: Launch WPS PDF and open the interactive PDF document that contains the problematic reset button.
- 3. Navigate to Form editing: Switch to the 'Form' tab on the top ribbon to reveal the interactive form field editing tools.
- 4. Adjust button properties: Double-click the Reset button to access its properties and modify or remove the unsupported mobile JavaScript actions.
- 5. Save and export: Save your optimized PDF form. You can now easily share it to your mobile device knowing it will function smoothly.
Frequently Asked Questions
Why does my JavaScript alert only show an 'OK' button on mobile?
Mobile PDF applications, including Acrobat Reader for Android and iOS, feature stripped-down JavaScript engines to optimize performance and security. They do not support conditional logic for alert dialogs, which restricts all prompts to a basic 'OK' confirmation.
Is the resetForm() JavaScript function supported on mobile?
Yes, the core resetForm() function is supported on most mobile PDF readers. The issue arises only when you attempt to bind its execution to a conditional response from a Yes/No pop-up dialog, which mobile apps cannot generate.
How can I prevent accidental form resets on mobile if I remove the confirmation dialog?
Without a confirmation dialog, the best workaround is to redesign the layout of your PDF form. Move the Reset button to the very bottom of the document or place it on a separate page to minimize the risk of users accidentally tapping it while scrolling.
