Hi Chris,

Let's dive right in...

1) Glad it's being of use!

2) I'm not sure I can replicate this. The behavior (should be) as follows:
user mouses over menu item, a short delay and the menu displays OR user
clicks menu item and immediately menu displays. Can you provide an example
somewhere?

My other thought is if you're referring to the user not being able to click
anywhere in the current list item to activate the menu. It should take this
into account but the only case where this doesn't happen is when a width
hasn't been applied and the user is using Internet Explorer AND there's a
sub menu. So... one work around is to make your link tags display: block so
they'll fill the entire LI tag and solve his problem. The CSS would be
similar to:
ul.jd_menu ul li a {
   display: block;
}

3) This has been fixed in the latest 1.3.beta2. You can fix this in the
1.2.1 version by doing something similar to:
ul.jd_menu a,
ul.jd_menu a:link,
ul.jd_menu a:visited,
ul.jd_menu a:active {
   color: #your color;
}

See if 1.3.beta2 solves this for you.

Cheers,
-Jonathan



On 3/8/07, Christopher Jordan <[EMAIL PROTECTED]> wrote:

Jonathan,

First of all, thanks so much for the great plug-in! I'm using it in my
latest project, and it's really made an impression on my client, and what
they think about my work. So thanks for the boost, there buddy! :o)

Secondly, I'm using the 1.2.1 version, but there's a behavior I don't
particularly dig, and I'm wondering if it's been "fixed" in the newest
version. I'm talking about the fact that in order to activate a menu option,
the user has to click on the text of the menu.

I thought this was because I was using anchor tags for my menu options so
I switched to spans. No dice. This has been my complaint about other menus
before.

Thirdly, (and it's possible this is also fixed in the newest version) if I
*do* use anchor tags for my menu items, once an option has been selected, it
no longer changes the text color for the hover. It takes on the visited
color (I guess). I'm not a CSS guru, and some of these things may seem
basement, but for me it's a bit more like trial and error. Sorry for that. I
feel like it's something I should have been able to fix in the css myself,
but just couldn't make it happen.

Any thoughts on these items? I read somewhere that the next version is a
complete rewrite, but I didn't see any of my concerns addressed -- probably
because they're only *my* concerns. :o)

Anyway, I hope to hear from you or anyone who knows about these issues.

Thanks heaps!
Chris

Jonathan Sharp wrote:

 Finally! After 15" of snow and moving into a house this past weekend, I
finally got beta2 out the door!

Thanks to all of your feedback and testing! A number of issues have been
fixed and we found a bug in the dimensions plugin (with IE) that Brandon
Aaron fixed promptly.

Changes:
- Menu supports absolute positioning
- Rewrote menu positining code
- jQuery 1.1.2 support

http://jdsharp.us/code/jQuery/plugins/jdMenu/1.3.beta2/

There's a beta2.zip which contains the code and demo for easier
downloading.

Please provide feedback and report any issues you may have.

Cheers,
-Jonathan

------------------------------

_______________________________________________
jQuery mailing [EMAIL PROTECTED]://jquery.com/discuss/


-- http://cjordan.info


_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/


_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Reply via email to