My example uses 1.2.1 right now. Does that matter, or should I do the
upgrade before put out any example code?
Chris
Jonathan Sharp wrote:
Trimming message...
On 3/9/07, *Christopher Jordan* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I will indeed upgrade to the beta (any idea when you'll call it a
stable release?), and see if it fixes problem number three. :o)
I'm about ready to stamp stable on it. I've fixed a few minor things
but need to write the documentation for it. We just moved last weekend
and don't have internet at our house (they're telling me Monday) so
early next week is when I should get everything online. There are only
a few lines of changes to the beta2 so if you use that all you'll have
to do for the stable release is drop in the new js file.
Also, a behavior I hadn't remembered to tell you about (which
might also be fixed in the latests beta) is that by default you
set the width of each menu to a certain number of pixels (115px if
memory serves). This meant that when I had a menu option that
exceeded this width, it would just spill out over the side. I
found a guy in the jQuery IRC channel that suggested replacing
that pixel width with a percent. He suggested 97% and so that's
what I used. This worked brilliantly to fix the problem... except
for FF. It produced an interesting effect where in when each time
I hover over a menu item the width of the menu grows. it's very
strange.
Ug...percents... I did see this in one case and using pixel values
solved it (except that you have fixed widths). If you post an example
I'll take a look at it then and see what I can come up with. It may be
as simple as creating a FF specific rule.
Cheers,
-Jonathan
------------------------------------------------------------------------
_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
http://www.cjordan.us
_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
