Last Comment Bug 183913 - absolutely positioned boxes in relatively positioned inline bug + hover bug
: absolutely positioned boxes in relatively positioned inline bug + hover bug
Status: RESOLVED DUPLICATE of bug 184897
:
Product: Core
Classification: Components
Component: Layout (show other bugs)
: Trunk
: x86 Linux
: P3 normal (vote)
: ---
Assigned To: layout
: Hixie (not reading bugmail)
Mentors:
http://glandium.org/test.html
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-06 07:19 PST by Mike Hommey [:glandium]
Modified: 2003-04-06 06:54 PDT (History)
3 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Mike Hommey [:glandium] 2002-12-06 07:19:03 PST
User-Agent:       Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021204 Debian/1.2.7-4
Build Identifier: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021204 Debian/1.2.7-4

On the page http://glandium.org/test.html there are 2 bugs :

the first one, (i think) is about the positioning of the span, which should be
just under the text (ie. no margins)

the second one is that when hovering the link, the span correctly disappears,
but doesn't reappear when mouse stops being on the link. If the display
attribute is inverted (ie. none for a .plop and block for a:hover .plop), the
span doesn't appear at all.

The same effect is seen when playing with visibility instead of display.

Note: adding top: 0px; left: 0px for positionning the span shows a strange thing
(see http://glandium.org/test2.html )

Reproducible: Always

Steps to Reproduce:
Comment 1 Boris Zbarsky [:bz] 2002-12-06 08:46:23 PST
Please file separate bugs for each problem...

This is all likely caused by the mess that is rel-pos-inlines as containing
blocks.... :(
Comment 2 Andrew Schultz 2002-12-11 18:56:37 PST
assuming this bug is now for the margin issue and bug 184899 is for the hover
problem, this bug is WFM with linux trunk build 20021210 although 1.2.1 displays
as you have described.
Comment 3 Mike Hommey [:glandium] 2002-12-12 14:22:17 PST
Oops, I also opened an other bug for the margin issue : bug 184897, sorry
Comment 4 Andrew Schultz 2002-12-12 15:27:16 PST
so what is this bug for?
Comment 5 Mike Hommey [:glandium] 2002-12-12 15:39:21 PST
right now, nothing, since both parts have been resubmitted (bug 184897 and bug
184899).; sorry again.
I don't know if i should change resolution to invalid or mark it as a duplicate
of one of the resubmitted bugs...
Comment 6 Andrew Schultz 2002-12-12 16:53:14 PST
*** Bug 184897 has been marked as a duplicate of this bug. ***
Comment 7 Chris Casciano 2003-04-05 20:12:57 PST
ok... after all the duping I'm gonna reask the question posed in comment 4...
"so what is this bug for?"
Comment 8 Andrew Schultz 2003-04-06 05:45:27 PDT
this bug is for the margin issue:
> the first one, (i think) is about the positioning of the span, which should be
> just under the text (ie. no margins)
Comment 9 David Baron :dbaron: ⌚️UTC+2 (mostly busy through August 4; review requests must explain patch) 2003-04-06 06:54:50 PDT
That would be much clearer if things were marked duplicate in the other direction.

*** This bug has been marked as a duplicate of 184897 ***

Note You need to log in before you can comment on or make changes to this bug.