V. cool.  (And I may have to put this on my calendar: Something that
IE does that's so handy it's worth emulating in other browsers!  Kind
of like 1999's XHR all over again.  So that's twice, then.)

Any idea when this will go into core?  Seems like it was done and well-
received before the 1.6 release, and a diff was created for RC1, but
it doesn't seem to have made it into the official release...
T.J. Crowder
tj / crowder software / com

On Mar 7, 7:37 pm, kangax <[EMAIL PROTECTED]> wrote:
> Walter,
> take a look at this patch - it should solve your 
> problemhttp://dev.rubyonrails.org/ticket/8354
> - kangax
> On Mar 7, 9:55 am, Walter Lee Davis <[EMAIL PROTECTED]> wrote:
> > I have a set of observers applied to a div to make a child of that
> > div (a close box) appear or disappear when the parent div is moused
> > over/out. I am seeing some very odd behavior and I am not sure where
> > to start looking for clues.
> > I'm using the latest Prototype and Scriptaculous.
> > An absolutely positioned DIV contains an inline table and a child
> > absolutely positioned div containing the close button. The close
> > button is set to appear when the parent DIV is moused over, and it
> > does. The close button is set to disappear when you mouse out of the
> > parent DIV.
> > Unfortunately, the mouseover / out event fires every time you cross
> > any sort of child content boundaries. So in this case, it fires when
> > you move over one cell or another in the table, or when you cross one
> > of the paragraphs inside one of the table cells. So the close box
> > appears and disappears with sickening frequency.
> > Does this ring a bell for anyone? I have tried a whole lot of
> > different approaches to fix this, but nothing seems to work.
> > Walter
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Spinoffs" group.
To post to this group, send email to rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to