Huge image scaling

Technical assistance
1

Infos:

  • Used Zammad version: 6.5.2-1763472134.c8495510.bookworm
  • Used Zammad installation type: (source, package, docker-compose, …)
  • Operating system: Package
  • Browser + version: Firefox Browser + 145.0.2

Expected behavior:

  • No scaling of images when copying them with Ctrl+C and pasting them with Ctrl+V.

Actual behavior:

  • If you copy content with images from a previous email or internal note using Ctrl+C and then paste it into a new reply, new note, new ticket or also in a knowledge base article using Ctrl+V, the images contained therein will be scaled up significantly.
  • To avoid this, you currently have to mark and edit each image in the new answer/note/ticket or knowledgebase entry once (for example, resize it again using the interactors). Only then will the image return to its original size.

Steps to reproduce the behavior:

Copying an email or internal note message with images per CTRL + V within a new reply
Simply copy content (e-mail or internal note) with images using Ctrl+C into a new internal note/e-mail reply/new ticket or into a knowledge base entry using Ctrl+V.

Then select one image with the left mouse button—the image will then be displayed in its original size again. As soon as you deselect it, however, it will be displayed oversized again.

To resize the image:

Select the image again.
Use one of the interactors at the corners to scale the image minimally.
Click again with the left mouse button.

2

Maybe it’s related to this bug report, but only an idea.

3

Hi @EGR_Supportteam

It works as intended for me. Am I doing something differently than you? Maybe you could provide some additional information. :slight_smile:

imgcopy

4

Yes this seems to be the same issue. However, we have not only done this with images from signatures, but also with others from emails.

5

2025-12-11_16h59_14

Hi bialaps,
Not really.
The image is selected with the mouse, copied with Ctrl+C, and pasted with Ctrl+V.

6

Thank you for the additional info. Let’s see what the outcome of the linked issue will be. I’m positive that this may also fix the issue here.

7

Hi @EGR_Supportteam

We’ve fixed the related issue, and the update for stable will be available shortly. This should also resolve the issue you described here. If it doesn’t, please let me know.

1 Like
8

Hi Bialaps,
Great! Thank you. We will gladly test it as soon as the new version is available.

9

It is available in stable since last week.

1 Like
10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.