Open Bug 1808112 Opened 2 years ago Updated 2 years ago

Editor: Resizing an image from the top-right corner sometimes won't preserve aspect ratio

Categories

(Core :: DOM: Editor, defect)

defect

Tracking

()

UNCONFIRMED

People

(Reporter: Fabrice.Neyret, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0

Steps to reproduce:

resizing an image in the composer, using the top-right corner handle so as to preserve aspect ratio.

Actual results:

from time to time ( not very often ), the "preserve aspect ratio" is ignored.
I such case I undo then re-grab and move slowly and then it works.

Expected results:

"preserve ratio" mode is supposed to work 100% of times ;-)
Especially when undo + re-acting slowly then do it correctly.

That's weird! That should be technically impossible. Wfm on TB 102.6.1 (64-bit), Win10.
Nothing which Thunderbird could do about this, because 1) it's not reproducible, 2) it's Editor territory. It's also a bit of an edge case ;-)
Anything in Tools > Developer Tools > Error Console (Ctrl/Cmd+Shift+J)?

Severity: -- → S4
Component: Untriaged → DOM: Editor
Flags: needinfo?(Fabrice.Neyret)
Product: Thunderbird → Core
Summary: resizing an image from the top-right corner not always preserve aspect ratio → Editor: Resizing an image from the top-right corner sometimes won't preserve aspect ratio
Version: Thunderbird 102 → unspecified

I didn't know the console. wow, many red/yellow things in there !
( well, reds are mainly many instances of

  • NS_ERROR_NOT_AVAILABLE: PreferDisplayName: undefined - not a boolean AddrBookCard.jsm:364
    getPropertyAsBool resource:///modules/AddrBookCard.jsm:364
  • NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIAutoCompleteInput.popup] LoginManagerChild.jsm:250
    observe resource://gre/modules/LoginManagerChild.jsm:250
    handleEnter chrome://global/content/elements/autocomplete-input.js:580
    handleKeyDown chrome://global/content/elements/autocomplete-input.js:545
    AutocompleteInput chrome://global/content/elements/autocomplete-input.js:40
    )

About the bug related to this report:
Note that I'm using copy-past of images without datacontent copy, since firefox allows to just copy the html image block (very useful to keep emails light when containing images from the web ).

→ I just tried with images from various site. I got the bug when trying to resize several times this image from boredpanda: https://www.boredpanda.com/blog/wp-content/uploads/2023/05/birds-memes-funny-images-645b86485ec10__700.jpg ( but I guess copy-past also get the full html image block : <img class="image-size-full" loading="lazy" data-index="0" src="https://www.boredpanda.com/blog/wp-content/uploads/2023/05/birds-memes-funny-images-645b86485ec10__700.jpg" alt="Birds-Memes-Funny-Images" title="Birds-Memes-Funny-Images" width="700" height="598"> ).
At copy-paste I got these messages in the console:
But no more messages appeared during the resizes.

Nodes added to message: 1 compose_script.js:10:15
<IMG> found, source is https://www.boredpanda.com/blog/wp-content/uploads/2023/05/birds-memes-funny-images-645b86485ec10__7… compose_script.js:22:15
Image not yet loaded compose_script.js:53:17
Image now loaded, calling maybeResizeInline compose_script.js:48:21
<IMG> found, source is https://www.boredpanda.com/blog/wp-content/uploads/2023/05/birds-memes-funny-images-645b86485ec10__7… compose_script.js:22:15

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://www.boredpanda.com/blog/wp-content/uploads/2023/05/birds-memes-funny-images-645b86485ec10__700.jpg. (Reason: CORS header ‘Origin’ cannot be added).

TypeError: NetworkError when attempting to fetch resource.
maybeResizeInline moz-extension://6e3b6c0a-4ca5-4419-a3cd-3284295da13c/compose_script.js:94
maybeResizeInline moz-extension://6e3b6c0a-4ca5-4419-a3cd-3284295da13c/compose_script.js:49
compose_script.js:121:15

Flags: needinfo?(Fabrice.Neyret)
You need to log in before you can comment on or make changes to this bug.