Details
Bug
Major
Description
The ICEPdf viewer not updating the value properly for the other acroform field with the same name.
For ex., in the attached document, if I update the 'Name' text box in the first page using the viewer RI Component, in the second page there is the same acroform field with the same name as 'Name', which is not updating properly. Sometimes it updates the value and sometimes not. Though the value is updating sometimes, the value is not same if you click/select the 2nd 'Name' text field, it's displaying the old value. Snaps attached for reference.
Please let me know if you need further details regarding the same.
For ex., in the attached document, if I update the 'Name' text box in the first page using the viewer RI Component, in the second page there is the same acroform field with the same name as 'Name', which is not updating properly. Sometimes it updates the value and sometimes not. Though the value is updating sometimes, the value is not same if you click/select the 2nd 'Name' text field, it's displaying the old value. Snaps attached for reference.
Please let me know if you need further details regarding the same.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Hi Patrick,
Do you have any update on this ticket?
Thank you.
Show
Naveen Anamaneni
added a comment - Hi Patrick,
Do you have any update on this ticket?
Thank you.
Yes I do.
As you noticed the fields are actually the same node in the AcroForm tree. We've never actually seen this before in our samples and didn't take this into account in our initial design. We'll need to likely add a property change event to correct the problem
We don't think it will be to difficult to fix and have targeted it for 6.3.
Show
Patrick Corless
added a comment - Yes I do.
As you noticed the fields are actually the same node in the AcroForm tree. We've never actually seen this before in our samples and didn't take this into account in our initial design. We'll need to likely add a property change event to correct the problem
We don't think it will be to difficult to fix and have targeted it for 6.3.
Thanks Patrick, for the update and considering the scenario in further release.
Shall we have some tentative date for release 6.3? And, please confirm whether this fix is considered or not in 6.3 release if it is in progress.
Show
Naveen Anamaneni
added a comment - Thanks Patrick, for the update and considering the scenario in further release.
Shall we have some tentative date for release 6.3? And, please confirm whether this fix is considered or not in 6.3 release if it is in progress.
Unfortunately I had to push this one forward to the maintenance release. Will get back on it one 6.3.0 is release.
Show
Patrick Corless
added a comment - - edited Unfortunately I had to push this one forward to the maintenance release. Will get back on it one 6.3.0 is release.
Thanks for the detailed report. I'll take a closer look today.