Multiple nested tooltips, child mouseout closes parent

[Spazsquatch]

...at least I think that's what is happening.

I'm using qTip load and external page. That external page contains a column of inactive buttons that have their own qTips that display topMiddle when the user hovers over them. The top button works correctly, but the second or third buttons result in an unexpected close of the parent qTip if I mouseout toward the top of the button, where the child qTip is located.

For the record I'm using parent and child to refer to their relationship onscreen, I don't believe there is an actual hierarchy to the qTips.

Here is a URL where the pattern can be observed.

1. On the link above hover over the "Babies" link, it should bring up a qTip with a larger preview and to the right 2 buttons along with show times.
2. Hover over the 1st button and you'll get a green qTip with some additional information. Roll up to mouseout, the green qTip closes.
3. Hover over the 2nd button and you'll get a green qTip with some additional information. Roll up to mouseout, the green qTip and the preview qTip close.
4. Hover over the "Babies" link and then over the 2nd button. Roll down to mouseout, the green qTip closes.
   

My guess is that I'm rolling over an element which is above the preview qTip and triggers a mouseout call to the preview qTip. I tried switching the event to mouseleave but the effect was the same. Can you shed some light on what is happening here, I'm out of ideas on how to deal with this (ultimately small but bothersome) issue.

Thanks

[Craig]

Hmm it's probably to do with the way the hide.fixed functionality is programmed in the RC3 release... I'd suggest trying qTip2 to most but I'm not sure if you'd be willing to spend the time doing so as it looks quite nicely integrated atm. Looking at what you're using qTip for this would definitely be a good idea regardless as RC has some quite bad performance issues, especially when using them in the quantities you are.

There is one thing I can think of that might help fix this issue: make the green qTip's position.container element the preview qTip. That might fix this.

[Spazsquatch]

I have not had a chance to look into your suggestion, but I wanted to jump in a say thanks. I'll let you know how it goes when I get a chance.

If not I'll see what moving to qTip2 will take. Probably not enough time before launch to consider it.