Closed
Bug 690131
Opened 13 years ago
Closed 13 years ago
text-overflow: ellipsis; causes images not to be displayed
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
DUPLICATE
of bug 690187
People
(Reporter: j, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
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 ...
Updated•13 years ago
|
Attachment #563203 -
Attachment mime type: text/plain → text/html
Comment 1•13 years ago
|
||
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)
OS: Linux → All
Hardware: x86_64 → All
Comment 3•13 years ago
|
||
That's expected, for now...
Summary: text-overflow: ellipsis; causes images to be replaces by ... → text-overflow: ellipsis; causes images not to be displayed
Comment 4•13 years ago
|
||
This is the correct rendering per the relevant specs: http://dev.w3.org/csswg/css3-ui/#text-overflow "... 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": http://www.w3.org/TR/CSS21/visuren.html#inline-boxes "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."
Comment 5•13 years ago
|
||
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.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Comment 6•13 years ago
|
||
> 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.
Comment 7•13 years ago
|
||
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 Thanks.
Comment 8•13 years ago
|
||
> For this particular issue/bug, let's start tracking real world URLs Yep. See the bugs blocking bug 312156 and their duplicates, if any.
Comment 10•12 years ago
|
||
The specification changed an this might be fixed soon.
Resolution: INVALID → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•