Issues with height parameter and compatibility with Obsidian's new resizing feature

[Mug521]

First of all, credit where credit is due: I've been using this plugin for a while now, and I have to say it's a key part of my workflow. I truly appreciate such a great creation 👏.

📌 Note: Obsidian has already launched an option to resize images by dragging from the edges. However, Image Converter's "Enable scroll-wheel resize" option is still better for a faster and more seamless workflow. You don't even have to move the cursor to the edge; just by holding the key and using the scroll wheel you get the work done ✅ (way faster than resizing from the edges).

That said, here are the details of the issues:

Is your feature request related to a problem? Please describe.

I remember that some time ago, this plugin did not add the height when resizing (it used to be just width), and there were no issues. Since the height parameter was introduced, I've started to see some undesired behaviors—such as adding new parameters to images that were already resized. These images already had a size parameter for the width, but instead of updating it, the plugin adds extra ones. (Note: I don't see this behavior every time).

For users who don't use the height parameter at all —and in my experience this is the only plugin I've found among many that creates this extra height parameter— the extra characters of the height add unnecessary clutter. In my case, I have to manually delete them after resizing each image to prevent this. It would be great to have an option to disable the height parameter from being added during resize 👍.

The expected behavior would be to have the best of both worlds:

1. Being able to resize images using Obsidian's native feature.

2. Being able to resize images using the "Enable scroll-wheel resize" option from Image Converter.

→ I just tested resizing an image with Obsidian's new native feature, followed by a scroll-wheel resize using the plugin, and the issue with extra parameters appeared again:

⚠ And there is another issue: after resizing an image using the scroll-wheel, I am unable to resize it by dragging the edges with the new Obsidian feature. It just doesn't work —nothing happens when I try to drag the edges in these scenarios. I have to close the note and reopen it to make the native function work again.

Describe the solution you'd like

1. The option to disable the height parameter when resizing an image. This would be more aligned with Obsidian's native resize feature which only uses one value for the width.

2. The option for scroll-wheel resize to be compatible with the native edge-dragging feature. Perhaps by eliminating the height parameter this could be solved—just a thought, as I am not sure. The goal is to ensure both methods can coexist seamlessly.

Related issues

I found that this issue with the height parameter has already been reported in other contexts, so it is a feature that has been requested before. I'll paste the links here for reference:

• [FEATURE REQUEST] Non-destructive Image Resizing: Add option to remove height from the link  #354
• [FEATURE REQUEST] Option to only add the width to the markdown when using the diagonal handles #183

Additional FR

This is an additional and secondary request —the ones above are the key ones— that I believe would add even more value to this already great plugin: the ability to set a default starting size for images —for example, choosing 400 as the initial width—. This way, when resizing an image for the first time, it starts at that specific width.

---

Thanks again for your time and for this amazing tool. I'm happy to provide more details or tests if needed.