Created attachment 563203 [details]
image inside of div with text-overflow: ellipsis; get replaced by ellipsis
Placing an Image inside of a div that has text-overflow: ellipsis;
The Image is not show.
Test case attached and visible at http://0x2620.org/html/bugs/Firefox7_elipsis.html
Other browsers show the image instead of ...
Jan, that's what the spec says to do.
Tantek, how many of these do we need before the spec changes? ;)
Mozilla/5.0 (Windows NT 5.1; rv:10.0a1) Gecko/20111014 Firefox/10.0a1
NOT fixed with bug 684266 (image isn't displayed)
That's expected, for now...
This is the correct rendering per the relevant specs:
"... implementations must hide characters and atomic inline-level elements at the applicable edge(s) of the line as necessary to fit the ellipsis/string"
images are "replaced inline-level elements" and thus "atomic inline-level":
"Inline-level boxes that are not inline boxes (such as replaced inline-level elements, inline-block elements, and inline-table elements) are called atomic inline-level boxes because they participate in their inline formatting context as a single opaque box."
I don't think the spec will change in this regard, but please reopen if it does.
If you want to raise a spec issue, the www-style mailing list is right forum.
> I don't think the spec will change in this regard,
That sort of depends on how web-incompatible this behavior is.... from what I can see so far, it's pretty web-incompatible.
Boris, how do we decide "how web-incompatible" anything in particular is?
For this particular issue/bug, let's start tracking real world URLs - since that's what should determine "web-incompatible" or not.
I've created a wiki page/section for this: https://wiki.mozilla.org/CSS/text-overflow#issues
> For this particular issue/bug, let's start tracking real world URLs
Yep. See the bugs blocking bug 312156 and their duplicates, if any.
*** Bug 703360 has been marked as a duplicate of this bug. ***
The specification changed an this might be fixed soon.
*** This bug has been marked as a duplicate of bug 690187 ***