![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
My webpage with a free textbook has a simple html navigation. Moving the cursor on the menu item makes appear the menu item red, using onmouseover. If I click that menu item, I get to the new page. Everything works fine. But if I then bo back with the back button (Mac Safari and IE - have not checke on PC yet) I do get back to the previous page, but with the choice of the next already/still highlighted. (There are two red bars in this case.) Ugly. All the programming is in html pages and in one css file; nothing is hidden. (See http://www.motionmountain.net ) What is going wrong? How can one avoid this? |
|
weblog | http://home.wanadoo.nl/b.de.zoete/_private/weblog.html | webontwerp | http://home.wanadoo.nl/b.de.zoete/html/webontwerp.html | zweefvliegen | http://home.wanadoo.nl/b.de.zoete/html/vliegen.html | `-------------------------------------------------- --<--@ ------------' |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
What is focus? I have never used the term in my stylesheet. |
|
weblog | http://home.wanadoo.nl/b.de.zoete/_private/weblog.html | webontwerp | http://home.wanadoo.nl/b.de.zoete/html/webontwerp.html | zweefvliegen | http://home.wanadoo.nl/b.de.zoete/html/vliegen.html | `-------------------------------------------------- --<--@ ------------' |
#5
| |||
| |||
|
|
My webpage with a free textbook has a simple html navigation. Moving the cursor on the menu item makes appear the menu item red, using onmouseover. If I click that menu item, I get to the new page. Everything works fine. But if I then bo back with the back button (Mac Safari and IE - have not checke on PC yet) I do get back to the previous page, but with the choice of the next already/still highlighted. (There are two red bars in this case.) Ugly. |
|
All the programming is in html pages and in one css file; nothing is hidden. (See http://www.motionmountain.net ) What is going wrong? How can one avoid this? Any hint is appreciated. Regards Christoph Schiller |
#6
| |||
| |||
|
|
My webpage with a free textbook has a simple html navigation. Moving the cursor on the menu item makes appear the menu item red, using onmouseover. If I click that menu item, I get to the new page. Everything works fine. But if I then bo back with the back button (Mac Safari and IE - have not checke on PC yet) I do get back to the previous page, but with the choice of the next already/still highlighted. (There are two red bars in this case.) Ugly. |
#7
| |||
| |||
|
|
Ugly? It reminds the user that he's already visited the page to which the link leads. That's useful, and it's been normal browser presentation since the beginning of graphical browsers. |
#8
| |||
| |||
|
|
On 10 Apr 2005 00:08:03 -0700, chri_schiller (AT) yahoo (DOT) com wrote: tr td class="lmenu" onmouseover="this.className='lmon'" onmouseout="this.className='lmout'" onClick="window.self.location='text.html'"><a href="text.html">Download</a></td /tr ... Anyway, when clicking on "back" the previous choise is still there, as if the pointer had remained over it - which it is not; the pointer is on the back button. Why? Seems that it's because there was never an "onmouseout" event generated. Maybe your onClick should call a function which does the onmouseout code and then loads the new page? (That's a wild guess, I haven't tried it.) Even better, why not get rid of all the JavaScript junk that won't work for a large percentage of the population anyway and do this all with the CSS a: pseudoclasses? |
#9
| |||
| |||
|
|
Greg Schmidt <gregs (AT) trawna (DOT) com> wrote On 10 Apr 2005 00:08:03 -0700, chri_schiller (AT) yahoo (DOT) com wrote: tr td class="lmenu" onmouseover="this.className='lmon'" onmouseout="this.className='lmout'" onClick="window.self.location='text.html'"><a href="text.html">Download</a></td /tr ... Anyway, when clicking on "back" the previous choise is still there, as if the pointer had remained over it - which it is not; the pointer is on the back button. Why? Seems that it's because there was never an "onmouseout" event generated. Maybe your onClick should call a function which does the onmouseout code and then loads the new page? (That's a wild guess, I haven't tried it.) Even better, why not get rid of all the JavaScript junk that won't work for a large percentage of the population anyway and do this all with the CSS a: pseudoclasses? Would you let me know how to do it? |
#10
| |||
| |||
|
|
I think you're looking for something like http://trawna.com/cssmenu.html |
![]() |
| Thread Tools | |
| Display Modes | |
| |