[sagaquisces]

I've been playing with a paging nav, both as text links in css and image rollovers in javascript, then css. At least in Mozilla 5, I'm finding that both a:hover and onMouseOver require mouse movement before firing. So here's the deal: blah.php?page=5 is loaded in my browser window with all content visible (no scrolling necessary)...I roll over, let's say, a "Previous" text or image link (doesn't appear to matter), I click, blah.php?page=4 loads with the navigation loading in the same spot in the browser window, with the mouse pointer still over the "Previous" link. The hover effect will not fire unless I move the pointer (even one pixel). Am I overlooking something obvious here, or is there a workaround, perhaps associated with the onLoad event, that checks to see if the mouse coordinates coincide with an element that has a hover style or onMouseOver event? I haven't experimented with an onClick event yet, but that is not passed to the subsequent loaded page, is it? Which would not solve my problem.

Thanks, Michael

[sagaquisces]

Since the project I'm working on an intranet, I can't point you to my example. But here is a link I found that uses css previous and next links similarly:

http://we04.com/gallery/index.cfm?StartRow=81

If you click on previous or next, the new view appears. If your pointer is still over the link when the new page view is loaded and you have not moved your mouse, the hover effect is gone in Mozilla 5, along with the link hand. In IE6 it works as expected (initially loses hover effect and link hand, but quickly updates at end of load).