We have logged another issue as PDFNET-48942 in our issue tracking system for your above case. We will surely check the feasibility of its implementation and let you know as soon as it is resolved. Furthermore, as shared earlier by @shahzadlatif - the issues are resolved on first come first serve basis under free support model. We have however recorded your concerns and will surely consider them during issue investigation.
Please also note that we encourage providing support via our free support forum and phone call support is only provided in case of paid support. In case you have more scenarios which need to be reported, you can please share them within this forum thread and we will address them for sure after testing the scenario in our environment.
We will surely resolve the logged issue, however it will be resolved on first come first serve basis as per the policy of normal support. We will surely inform you as soon as the tickets associated with this forum thread are resolved. We highly appreciate your patience in this regard. Please give us some time.
Above logged ticket is more like a new feature which needs to be added to the API. It would take certain amount of time to get investigated for feasibility and implementation. We will surely inform you within this forum thread as soon as we have some definite updates in this regard. We request for your patience in this matter.
Are you referring to another issue you are facing with some PDF? Please share a sample PDF document and code snippet so that we can replicate this issue at our side and address it accordingly.
We are afraid that earlier logged tickets have not been yet resolved. As soon as they are completely investigated, we will be able to share some ETA with you regarding their fixes. We highly appreciate your patience and comprehension in this matter. Please spare us some time.