Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose bounds on the PdfFormField class for the PdfViewer #1658

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jvanduppen
Copy link

Exposing the bounds on the PdfFormField class. Should not affect anything, other than giving the ability to see where on the page the form fields are being rendered.

@ramkumarsync
Copy link
Collaborator

Exposing the bounds on the PdfFormField class. Should not affect anything, other than giving the ability to see where on the page the form fields are being rendered.

We understand that you would like to see where the form fields are rendered on the page with the bounds information. However, could you please share the entire use case of exposing the bounds information in the form field? It will be helpful for us to understand the case deeper and consider this in our future releases.

@ramkumarsync ramkumarsync added the waiting for customer response Cannot make further progress until the customer responds. label Feb 13, 2024
@jvanduppen
Copy link
Author

Exposing the bounds on the PdfFormField class. Should not affect anything, other than giving the ability to see where on the page the form fields are being rendered.

We understand that you would like to see where the form fields are rendered on the page with the bounds information. However, could you please share the entire use case of exposing the bounds information in the form field? It will be helpful for us to understand the case deeper and consider this in our future releases.

Our objective is to show widgets indicating a field is required or not following the proper format when submitting a PDF Form similar to forms with required fields in html
image

@VijayakumarMariappan VijayakumarMariappan added pdf viewer PDF viewer component open Open and removed waiting for customer response Cannot make further progress until the customer responds. labels Mar 6, 2024
@immankumarsync
Copy link
Contributor

@jvanduppen,

We have analyzed this case of exposing the bounds information of form fields, and we are exposing only the form field in our SfPdfViewer widget. Some form fields have child items within them that can be placed anywhere on the page, and these child items are not exposed in the form field collection obtained from the PdfViewerController.getFormFields method. Hence, exposing the bounds only for the form fields will not be complete if the child item is not exposed. Additionally, this bounds information is in the PDF page coordinate system. If you display a widget using this bounds value as is, the widget won't be displayed near the form field in the PDF viewer.

This feature requires more in-depth analysis, and we do not have any immediate plan to implement the support for “Exposing bounds for the form fields”. At the planning stage of every release cycle, we review all open features and identify features for implementation based on specific parameters including product vision, technological feasibility, and customer interest. We will let you know here when this feature implementation is started in the future.

Kindly use the feedback link to track the status of the feature, https://www.syncfusion.com/feedback/51948/expose-bounds-for-the-form-fields-in-the-pdfviewer

@ramkumarsync ramkumarsync added uncertain Uncertain feature and removed open Open labels Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pdf viewer PDF viewer component uncertain Uncertain feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants