HTML to PDF - img with height only (or width only) is not rendered proportionally

Aspose.Words Product Family
1

Hello.

Using Aspose-words 16.4.0 there is an unusual behavior about HTML parsing when saving to PDF, PNG or DOC.
It seems that the Aspose library, in case an img tag is missing either width or height property, simply renders the image using its native width or height, respectively, in pixel.
As stated here and here and verifiable with FireFox, Internet Explorer, Chrome and Thunderbird, usually HTML renderers calculate the missing dimension proportionally to the given one. E.g. if the missing one is the width, the calculated value for it is set to ImageWidth * height / ImageHeight; instead, if the missing one is the height, the calculated value for it is set to ImageHeight * width / ImageWidth.

Is there a way to make Aspose-words behave as browsers? If not, could you please add, likely as an option, this feature to be compliant with usual browsers’ behavior?

Thank you in advance.

Regards,

Renato MAURO

2
Hi Renato,

Thanks for your inquiry. We have logged this feature request as WORDSNET-13603 in our issue tracking system. You will be notified via this forum thread once this feature is available.

We apologize for your inconvenience.
3

Hi Tahir.

Thanks for your response. Is it possible to have an ETA about this feature?
Thank you so much.

Regards,

Renato

4
Hi Renato,

Thanks for your inquiry. We try our best to deal with every customer request in a timely fashion, we unfortunately cannot guarantee a delivery date to every customer issue. Our developers work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers.

Currently, the requested feature is pending for analysis and is in the queue. Once our product team completes the analysis of this feature, we will then be able to provide you an estimate.

Thanks for your patience and understanding.
5

The issues you have found earlier (filed as WORDSNET-13603) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
6

Thank you, Tahir.