ok, i got it, well, at least the problem. now, i'm not sure about how to solve it.
1/ maybe it's a css issue. in your stylesheet, try changing this #aboutus .nav .navmain a.current, #aboutus .nav .navsecondary a.current { color: #a5ee26; } #aboutus .nav ul.navsecondary { left: 130px; top: 115px; } #aboutus .nav .navsecondary a { color: #c87eeb; } into #aboutus .nav ul.navsecondary { left: 130px; top: 115px; } #aboutus .nav .navsecondary a { color: #c87eeb; } #aboutus .nav .navmain a.current, #aboutus .nav .navsecondary a.current { color: #a5ee26; } 2./ i noticed you use the function doShowStorywrap(c) sometimes passing it a jquery object, sometimes just "this". The case in which the rendering does not happen is when you don't use a jquery object, so i would try that, see if that changes anything. On Mon, Dec 22, 2008 at 4:10 PM, userdude <farri...@gmail.com> wrote: > > > Hi Alexandre, > > Thank you for the reply. I'm not sure what you mean by enable debugging in > Firebug. > > Basically, the first submenu item for specific menu item should always > default to having the "current" class. > > Although I can tell that something is occurring using console.log to inspect > the a-link addClass method, the actual html for the page rendering is not > applying; I effectively cannot see the results of the addClass method that > is run if I am doing an addClass method during only the main menu > selections. > > The best way to see what I mean is to: > > * first, click the "about us" link. > * then, click the "what we do" link > > The "what we do" link should be highlighted just like after the second click > when clicking on the "about us" link. As far as I can tell, addClass is > running, but the page is not actually rendering the change, and Firebug is > not showing the class in the HTML inspector. > > Right-click on the "what we do" link, select "Inspect Element", then click > on the "about us" link. See the current goes away? It should stay, and I > can't figure out why it's not working. > > Thanks! > Jared > > > Alexandre Plennevaux-2 wrote: > > > > jared, your website is supernice and promising, but i for one don't > > understand anything about your problem description. i think either you're > > lacking sleep or you wrote too fast :) > > > > Can you rephrase please, for people that don't yet know your website > > internals (or lack sleep themselves ) ?can you also enable logging (i have > > firebug) on the page online, because the console doesn't show anything > > here. > > > > Thanks > > > > alexandre > > > > On Mon, Dec 22, 2008 at 2:08 PM, userdude <farri...@gmail.com> wrote: > > > >> > >> > >> I am having an issue with the following jQuery code: > >> > >> http://www.houseofoverlord.com/c/jeniffer/bhive/test2.html > >> http://www.houseofoverlord.com/c/jeniffer/bhive/test2.html > >> > >> The rendering that is not occurring is when the page: > >> > >> * Loads > >> * When clicking the main (horizontal) menu items > >> > >> What is supposed to happen is the default (first) navsecondary a tag is > >> supposed to receive a current class designation. If I console.log, > >> everything seems fine, but the screen display does not show the change, > >> and > >> the HTML view in Firefox does not demonstrate the update > >> (class="current"). > >> > >> If you click on "about us" and then click on "what we do", that behavior > >> is > >> supposed to happen automatically when clicking the "about us" menu link. > >> > >> Anybody know what's going on? > >> > >> Thanks! > >> Jared > >> -- > >> View this message in context: > >> http://www.nabble.com/Bizarre-rendering-issue-%28FF-3%2C-IE-6%29-tp21127522s27240p21127522.html > >> Sent from the jQuery General Discussion mailing list archive at > >> Nabble.com. > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/Bizarre-rendering-issue-%28FF-3%2C-IE-6%29-tp21127522s27240p21129366.html > Sent from the jQuery General Discussion mailing list archive at Nabble.com. >