354319 - Broken image placeholder must be visible when in designMode

Status: NEW

(Core :: DOM: Editor, defect, P5)

Description

[FredCK]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7

When document.designMode="on", a typical broken image icon (placeholder) should be displayed so the user can select it to make changes in the image.

Reproducible: Always

Actual Results:  
Today, no image or placeholder is displayed at all, making it impossible to edit or move the image.

Comment 1

[FredCK]

Just open the URL in IE to see the expected behavior.

Comment 2

[Sorin Sbarnea]

I would like to see this 'feature' or at least a way of showing the broken images like IE.

Comment 3

[Robert Stopp (textrinum)]

If an image is broken in designmode, it needs an doubleclick to get selected, what is also an bug.
If an placeholder is impossible an "_moz_image_broken" attribute shut be appended to the img-element for a user-css.

Comment 4

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 5

[Robert Stopp (textrinum)]

Go to http://demo.textrinum.org , login and edit the "Lorem Ipsum" - page.
Give the sample image a wrong url.
In this case there is no Broken Image Palceholder and i can't say why. Using Firefox 3.6

By working on that: Opera gives at least images an fileSize member in the DOM.
Would be good for Firefox to.

Comment 6

[FredCK]

There is an URL in this ticket, so it's enough to open it to see that this is still a current issue.

Comment 7

[Nickolay_Ponomarev]

Attachment: testcase from the reporter

Comment 8

[Nickolay_Ponomarev]

That message was automated, sorry about that.

Comment 9

[Jet]

Firefox 22 out and this is still an issue.

Comment 10

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.