839850 - [contenteditable] <img> in contenteditable div has no event for resize

Status: RESOLVED INCOMPLETE

Description

[Rustam]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130201065344

Steps to reproduce:

<img> in contenteditable div has no event for resize.

Comment 1

[(mostly gone) XtC4UaLL [:xtc4uall]]

Testcase?

Comment 2

[Rustam]

Created attachment 712262 [details]
Test case

Comment 3

[Rustam]

I binded on <img> resize, resizestart, resizeend events. Works only in IE.

Comment 4

[(mostly gone) XtC4UaLL [:xtc4uall]]

(In reply to Rustam from comment #2)
> Created attachment 712262 [details]
> Test case

preferably without JQuery

Comment 5

[Rustam]

I don't know how to write this on pure javascript. But effect will be similar as with jQuery.

Comment 6

[Ioana (away)]

Reproducible with the attached testcase on:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:21.0) Gecko/20130211 Firefox/21.0.

Comment 7

[Paul Pasca[Away. Please needinfo? Paul Oiegas [:pauloiegasSV]]]

Hi Rustam,

I haven't managed to reproduce this issue on the latest release(43.0.4) nor latest Nightly(46.0a1). The resize worked as expected in both release and Nightly.

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20160105164030

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160111030207

Can you please try to reproduce this on the latest release(43.0.4) and latest Nightly(46.0a1) and provide the results? When doing this, please try to reproduce with a new clean Firefox profile, maybe even in safe mode, as some of this issues may be caused by third party installed add-ons or custom settings(https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems).

Thanks,
Paul.

Comment 8

[Paul Pasca[Away. Please needinfo? Paul Oiegas [:pauloiegasSV]]]

Since the reporter didn't provide the requested information, I will mark this issue as RESOLVED INCOMPLETE. If you still encounter this problem, please feel free to reopen this bug, or file a new one.