Do you have an issue with a specific file(s)?
No, every file with a Datepicker has the issue
Can you reproduce using one of our samples or online demos? Yes showcase.apryse.com has the same Problem
Are you using the WebViewer server?
No
Does the issue only happen on certain browsers?
Safari on MacOS/iOS
Is your issue related to a front-end framework?
No
Is your issue related to annotations?
WidgetAnnotations, yes
Please give a brief summary of your issue:
iOS: Datepicker isn’t opening
MacOS: Datepicker is opened, but after selecting a date or focusing another field it isn’t closed.
Please describe your issue and provide steps to reproduce it:
iOS: Open a PDF file with a datepicker on it (like the attached one). Tapping on the calendar to open the Popup for selecting a specific day isn’t working.
MacOS: Open a PDF file with a datepicker on it (like the attached one). Clicking on the calendar opens the popup. But after selecting a day or changing focus on another field the Popup stays open.
Please provide a link to a minimal sample where the issue is reproducible:
Can be tested with the attached file and https://showcase.apryse.com
As far as i can say the problem is the native Calendar integration. Maybe the option for the old Javascript Datepicker would be an option.
In the meantime a workaround would be great because it is preventing us from using our PDF-Forms.
Unfortunately, there is no known workarounds for this issue as it looks to a potential issue that came up from the DatePicker change in 11.13. However, it works as expected on WebViewer 11.12.
I was able to reproduce the issue with the steps provided and have added this to the backlog for the product team to review. We will let you know when we have additional information.
In the meantime, could you please share the impact of this issue for the product team to evaluate the priority?
to be honest this issue is a showstopper for us with the current release.
Since we’ll have to wait for the next release for the fix, we’ll downgrade to WebViewer 11.12 for now. So it’s no longer an urgent issue for us at the moment, but it would be great if the fix could be included in the next release.
We’ve now fixed this issue and it’s available in our latest nightly experimental build. See here for instructions on how to try out the nightly build https://docs.apryse.com/web/faq/webviewer-nightly-build. Let us know if it’s working for you.
This fix will be available in our next official release, which is scheduled for Aug 19. You can sign up for our product update email to be notified when a new release is available https://community.apryse.com/c/announcements/11
