Thanks for reaching out to WebViewer Support! We appreciate this bug report and are able to reproduce on our end. We’ve added this bug ticket to our backlog and will have it looked at in our next sprint. We cannot guarantee when exactly it will be fixed/released, but when it does we will let you know when a fix is available!
Let me know if you have any further questions.
PDFTron Systems, Inc.
Hi Wanbo, thanks for the update! Alex is currently unavailable but I’m a colleague of his and I just tested this again, both in your measurement tools demo and in our own application after updating our PDFTron dependency there to 8.11.0.
Unfortunately I can still reproduce the issue. To clarify, the steps to reproduce are as follows:
create a scale by using the “calibrate” tool and save it
select the newly created scale by clicking on it in the dropdown menu of available scales
click “calibrate” again to update the scale
click on the “update” button, which still throws a console error and does not update the scale
Step 3 is the important one here—the error only appears when attempting to update the scale via the “calibrate” option. Manually updating the values in the input fields works fine.
Please let me know if I can provide further input. Thanks!
Okay, but at what point do you publish to npm? Or more specifically, when do changes from nightly builds that come after the initial version of 8.11.0 end up on npm? Will they be part of 8.12.0 instead?
I ask because we use npm as our dependency manager and in order to be able to install all dependencies and build our app in an automated fashion, we need to use the version of PDFTron that’s published to npm.
Edit: Sorry, I should have actually checked your link before asking my question. I see that’s a list of versions on npm. Thank you, this should be all we need for testing!
Edit 2: Tested with 8.11.0-20230102 and can confirm that the bug is fixed, thanks a lot! Am I correct in assuming that 8.12.0 will be the next stable release to contain this fix?