Closed
Bug 35727
Opened 25 years ago
Closed 24 years ago
cannot move absolutely positioned elements that follow inline elements
Categories
(Core :: Layout, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: alecf, Assigned: alecf)
Details
(Whiteboard: [nsbeta2-])
Attachments
(1 file)
|
1.85 KB,
text/html
|
Details |
I'm trying to add those little popup windows to tinderbox for mozilla/gecko, and
I've run into kind of an odd problem.
I want to position a <div> above the other text with the current build's
comments, etc, and then move this div somewhere else on the page.. the problem
is that it won't move. I've narrowed the problem down to the location of the
<div> in the content model.
the div is:
<div id="popup" style="position: absolute; z-index: 1; top: 25px; left: 25px;">
my popup
</div>
and then using JS, I say
document.getElementById("popup").style.top="100px";
to move this popup somewhere else.
the problem is that if this div occurs anywhere in the document aside from
immediately after the <body> tag, the <div> will not move.
i.e.
this allows the <div> to move around the screen:
<body><div id="popup" ....> </div>
but this does not:
<body>Some text<div id="popup" ....> </div>
I've also tried preceding the <div> with another div (i.e. another block level
element) but it has the same problem.
if we can get this working, I can add the popup support to tinderbox - which
would be really nice.
|
Assignee | |
Comment 2•25 years ago
|
||
ok, in trying to make a test case for this, it looks like this may be more of an
event issue, I'm not sure. it seems like sometimes, and I'm not sure when, the
absolutely positioned div is stealing all events... what I was trying to do is
move a div when the mouse clicks on a link.. but sometimes the even never
actually hits the link.
so what may be happening is that under certain circumstances the click is
hitting the div, rather than the link.
I'll continue to poke at it, it seems to be behaving unpredictably right now.
|
|
Assignee | |
Comment 3•25 years ago
|
||
|
|
Assignee | |
Comment 4•25 years ago
|
||
the attached testcase actually seems to behave normally, but I'm attaching it
here for the sake of completeness
|
|
Assignee | |
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → M20
|
||
Comment 5•25 years ago
|
||
Nom. nsbeta2, recc. nsbeta2+ [some lenient bugfix-checkin-ok-date -], with
fall-through to nsbeta3+ hardstop if not fixed for nsbeta2+. This appears to be
a bug that could severely handicap the usability of Gecko as a platform for
DHTML-based applications and UIs, so I think it's a stopper for rtm at the
latest.
Putting on [nsbeta2-] radar.
alecf, should someone else get this bug?
Whiteboard: [nsbeta2-]
|
||
Comment 7•24 years ago
|
||
Alec, who should own this bug? I'm leaning toward minus if the answer is you.
|
|
Assignee | |
Comment 8•24 years ago
|
||
remarking worksforme. I was never able to reproduce
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•