15545 - {css1} Broken floating IMG elements dissapear [ALT]

Status: VERIFIED FIXED

(Core :: Layout, defect, P3)

Description

[Masatoshi Kimura [:emk]]

Step to reproduce:
1. Launch apprunner.
2. Go to the following attachment.

Expected result:
Floating, broken IMG elements should float and should not ignore width and
height because floating elements are block-level elements, NOT inline elements.

See the CSS2 spec. "9.7 Relationships between 'display', 'position',
and 'float'" and "10.3 Computing widths and margins".

Actual result:
The alternate text does not float and width/height gone.

I am using [1999100308] build on WinNT4 (SP5).

Comment 1

[Masatoshi Kimura [:emk]]

Attachment: testcase for floating, broken IMG

Comment 2

[Hixie (not reading bugmail)]

Stealing QA contact...

Comment 3

[Hixie (not reading bugmail)]

Attachment: Slightly better test case.

Comment 4

[Masatoshi Kimura [:emk]]

This seems to be fixed now except that the loading icon will not change
to the broken icon.

Comment 5

[troy]

*** Bug 22507 has been marked as a duplicate of this bug. ***

Comment 6

[troy]

*** Bug 22444 has been marked as a duplicate of this bug. ***

Comment 7

[John Morrison]

Adding testcase from bug 22444 -- just noting (for completeness) that behaviour
within tables can differ from the general case for flow :
   http://bugzilla.mozilla.org/showattachment.cgi?attach_id=4115

Comment 8

[Hixie (not reading bugmail)]

STEPS TO REPRODUCE:
Open http://bugzilla.mozilla.org/showattachment.cgi?attach_id=2001 in Mozilla.

ACTUAL RESULTS:
This is not fixed at the moment. We first lay out correctly, but upon finding
that the image doesn't exist, we currently DO NOT reflow the floater. A forced
redraw (e.g. invalidating the window by dragging it out of the screen and back
again) hides the floater. A reflow shows that the floater has in fact totally
dissapeared.

A reload places an IE-style "broken image" box with glyph.

EXPECTED RESULTS:
Once the image is found to not be available (whether during the initial flow
or later on) the IMG element should be treated as a normal element containing
the ALT text, as with non-floating broken IMG elements.

ADDITIONAL COMMENTS:
The bug at the moment seems to be that if the element is floating, the
CantRenderReplacedContent (or whatever it's called) fails. Troy?

VYV03354: Note that we do not ever want to see the "broken icon". See bug 1994
for more details on that.

Comment 9

[troy]

I know it's broken, that's why the bug is marked ASSSIGED...

Comment 10

[Hixie (not reading bugmail)]

Troy: I never suggested you might think otherwise -- I just figured that since
I had just investigated the problem, and had notes that were slightly more
detailed than currently included in this bug, I might as well file them too...
Since I'm QA contact, that would be my responsability, no? :-)

Comment 11

[troy]

Yup, it makes perfect sense. I was just chiming in that I'm aware of the
problme and do actually plan on fixing it some day. :-)

Comment 12

[Hixie (not reading bugmail)]

Migrating from {css1} to css1 keyword. The {css1}, {css2}, {css3} and {css-moz}
radars should now be considered deprecated in favour of keywords.
I am *really* sorry about the spam...

Comment 13

[troy]

Okay, this is fixed now. Turns out there were three separate problems that 
needed to be fixed.

Comment 14

[Masatoshi Kimura [:emk]]

We still see the "broken image" icon when we reload the page.

Comment 15

[troy]

I'm not sure I follow. It displays correctly the first time, but then if you 
reload the page you see the broken image?

If so, it sounds like a different problem

Comment 16

[Hixie (not reading bugmail)]

Main issue has been fixed. Opened bug 24815 to cover the reload problem.
VERIFIED.