Do you have an issue with a specific file(s)? no
Can you reproduce using one of our samples or online demos? yes, all of them that allow forms mode
Are you using the WebViewer server? no
Does the issue only happen on certain browsers? no
Is your issue related to a front-end framework? no
Is your issue related to annotations? no
Please give a brief summary of your issue:
The Open File, Print, and Download menu items are disabling in WebViewer 11.7.1 in edit forms mode, but did not do that in 11.3.
Please describe your issue and provide steps to reproduce it:
Go to a demo of 11.7.1 that allows forms edit mode, make sure a file is open, and put the editor into forms edit mode. Observe the menu items mentioned are disabled.
We recently updated our WebViewer package from 11.3 to 11.7.1, and have observed the previous behaviour. Is this a regression, or was the regression in 11.3 where the menu items did not disable? I don’t believe I’ve see a setting for this, and I know previous to 11.x this happened. I’m wondering why the flipflop?
Hello, I’m AiRon, an automated tech support bot While you wait for one of our customer support representatives, I can help you with your question.
It seems like you’re encountering a change in behavior regarding menu item availability in WebViewer’s form editing mode between versions 11.3 and 11.7.1. This could be due to an intentional change in the default behavior or a bug fix that aligns with the expected functionality where certain actions are disabled in form editing mode to prevent conflicts or data loss.
Some things you can try:
Check if there’s a configuration option that allows these menu items to be enabled in form editing mode. Sometimes, feature toggles are introduced to control such behavior.
Review the WebViewer documentation related to form editing to see if there are any notes on behavioral changes or new settings introduced in recent versions.
Consider implementing custom logic to re-enable these menu items if your use case requires them to be active during form editing.
Test the behavior in a controlled environment to ensure there are no other factors affecting the menu item state.
Here are some resources that might help you:
Forms Guide - This guide provides detailed information about working with forms in WebViewer.
Customization Guide - Learn how to customize the WebViewer UI, which might include enabling/disabling menu items.
Advanced Configuration - Explore advanced configuration settings that could affect menu item availability.
WebViewer FAQ - Check frequently asked questions for any related inquiries about version changes.
Hopefully, this helps you solve your problem while you wait for a human to get back to you.
The expected behaviour is to disable these specific menu items while in form field creation mode and in 11.7, has changed to match these settings. Does this change affect your workflow in any way?
Not really, our general practice is not to just disable things with no explanation, and we assumed that the limitation that required these to be disabled was removed in 11.x. We had verbiage near the editor that explained this, and removed it under that assumption.
In general we would expect these to not be disabled, but to display a popup that informs the user about what has happened, and allow them to choose the result they would like (something like “You are in forms editing mode, you cannot [INSERT_ACTION_HERE] while in this mode, would you like to exit forms mode and [ACTION], or stay in forms edit mode?”, with appropriate buttons.)
Is there some way I can implement something like that? Even automatically exiting forms mode and committing the changes if these actions happened would be better (optionally entering forms mode again afterward).
This implementation could be done with our custom modal that shows a custom message along with two different buttons that would either exit or stay in form field creation mode.
If you would like to enable or disable these elements, you can change them with the updateElement() API by targeting its data-element and setting the disabled property true or false. For example:
