Do you have an issue with a specific file(s)? No
Can you reproduce using one of our samples or online demos? Yes
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?
Please give a brief summary of your issue: Exposing Font in the Form Field Style Dialog/Panel
Please describe your issue and provide steps to reproduce it:
The Form Field style dialog/panel already allows an end user to change the font size of a form field, but it would be very beneficial if a user could designate a font for individual fields.
I am aware font can be set programatically but sometimes there are some fields that require a specific font that is unique from setting an overall PDF font for the document.
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.
To include font selection in the form field style menu in WebViewer, you’ll need to extend the existing functionality to allow users to choose a font for individual form fields. This is not directly available in the WebViewer UI, but you can achieve it by customizing the form field styling programmatically.
Some things you can try:
Use the setFont method to specify a font for a form field programmatically.
Create a custom UI component or extend the existing form field style panel to include a font dropdown.
Utilize the createInnerElement function on widget annotations to add custom elements that allow font selection.
Update the form field’s appearance after changing the font to ensure the changes are reflected visually.
Here are some resources that might help you:
Styling PDF form fields - Learn how to customize form fields, including adding custom DOM elements.
I will submit a feature request to add font styling to text fields in the UI.
While we cannot guarantee the implementation of this feature, we will add it to the backlog for our product team to review for feasibility and viability. Could provide some further information around the context of why you want the feature? We would be interested to know:
What is the workflow that you would use the requested feature in?
Why is the feature valuable to you and your users?
The main use case is when the static content of the PDF form has a specific font and then with tagging we’re looking to match that font.
I believe I can programatically set the font but I think a native UI solution would be best that an end user who can mark up the forms on their own. This puts the power in the hands of the end users.
Currently I think they’re using other PDF applications like Adobe pro to change the font of the form fields.