Closed
Bug 16604
Opened 25 years ago
Closed 24 years ago
relatively positioned linked images are invisible
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: heathh, Assigned: buster)
Details
(Keywords: css2)
4xP? Neither Communicator 4.5 nor IE 5 does this.
Linked images are invisible if the <a> tag is relatively positioned. I'm not
quite sure how to put this, so it's better explained by example:
<html>
<head>
<style type="text/css">
.uncle {position: relative;}
</style>
</head>
<body>
<a href="http://ournet.oursc.k12.ar.us/~javaking/coffee.html" class="uncle">
<img src="http://ournet.oursc.k12.ar.us/~javaking/coffee.gif"></a>
</body>
</html>
When you look at this in viewer, the image is not visible. However, the box for
the image seems to be there; the "hand" cursor appears where the image should
be, and you can click on the link.
Tested using M10 and 1999.10.15.11 builds for Win32 on Windows 98, with the same
results each time.
Moving the stylesheet reference to the <img> tag fixes the problem in viewer and
IE, but Communicator 4.5 is not pleased.
This is kind of nasty. Because of the way CSS2 defines vertical placement of
lines and their child boxes, the IMG frame ends up being positioned with a
y-offset of -660 twips and the Inline frame containing it has a frame height of
0
That means we end up sizing the associated view with a height of 0 as well, and
that's why the image isn't displayed...
This sounds like a result of the fix to 5821. Is the view not displayed because
there's some check that its height and width aren't zero before delving into the
painting...? (I'm guessing that because you have fixed overflow issues for
positioned elements already, unless they're broken again.)
There are two issues:
1. the relatively positioned inline code is slightly different from the code
that handles absolutely positioned elements
2. yes we handle (for absolutely positioned elements) the case of elements
overflowing outside the right and bottome edges. However, in this case the child
element is positioned above the parent, and none of the code handles that case
currently
|
||
Updated•25 years ago
|
Summary: relatively positioned linked images are invisible → {css2} relatively positioned linked images are invisible
|
|
||
Comment 4•25 years ago
|
||
Test case: http://www.bath.ac.uk/%7Epy8ieh/m/rel-pos-replaced.html
If an image is inside a relatively positioned element, things go awry (image
is not displayed.) If the image itself is relatively positioned, things are
fine. Weird things also happen to text edit boxes, but I guess that is another
bug. (I haven't filed one.)
|
|
||
Comment 5•25 years ago
|
||
Migrating from {css2} to css2 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...
|
||
Updated•25 years ago
|
Summary: {css2} relatively positioned linked images are invisible → relatively positioned linked images are invisible
|
Reporter | |
Comment 6•25 years ago
|
||
The page that originally showed me this problem and the test case below display
*mostly* okay with the M14 release builds for Win32 and i386 Linux, for what
it's worth.
re-assigned to me
Assignee: troy → buster
Status: ASSIGNED → NEW
Target Milestone: M17 → M19
redistributing bugs across future milestones, sorry for the spam
Target Milestone: M19 → M21
this bug was fixed a while back, forgot to mark it fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•