Well, not really - I ended up adding code to explicitly set the "top" and "left" of my div baseed on the top and left of the clickable trigger that makes it slide down and up. That was unpleasant to have to do, but it does actually work now.
By the way - the documentation doesn't do much of a job at explaining the difference between the "offset()" and "position()" routines, and I have a feeling that some of what is written there may not be 100% accurate. I find that I generally use "position()" instead of "offset()", but that's only based on empirical trials and not a real understanding of what those routines are and what they're for. On Wed, Sep 9, 2009 at 10:27 AM, kramers<kramers....@gmail.com> wrote: > > Did you ever find a solution to this problem? I ran into the same > issue. > > On Sep 3, 4:24 pm, "emmecin...@gmail.com" <emmecin...@gmail.com> > wrote: >> The online documentation for "slideDown" and "slideUp" says that only >> the height is affected by those routines. That claim is false: the >> value of "display" is also changed, and for me that's a problem. >> >> I have a div that's set up with "position: absolute" and >> "display:inline". I want that box to appear in the layout relative to >> its surrounding content, and that's the simplest way I know to do >> that. I also want the box to be animated. I do not, however, want >> jQuery to touch my "display" value, because setting it to "block" >> breaks the layout completely. >> >> Looking at the (not trivial to understand) code, it *appears* that the >> original value of the "display" attribute is saved, or rather that the >> code attempts to save it. However, that's not working for me: my div >> is definitely display:inline to start off, but a call to "slideUp" or >> "slideDown" always leaves it either "display: none" or "display: >> block". > -- Turtle, turtle, on the ground, Pink and shiny, turn around.
