[Javascript] Need help with IE events - FIXED

[Mike Dougherty]

I tried various ways of hooking up the onclick/onmouseover events, including setting the 
attributes in HTML.  I read countless google hits looking for insight.  Eventually I tried: 
 document.onmouseover = function() { window.status = event.srcElement.id }

I noticed that when the event failed, the ID in the status bar did not belong to the button. 
 After putting a border around the offending element(s) it was easy to see what was happening. 
 There was an empty <li> taking space in IE, (but not Firefox) which I earlier 'fixed' by moving 
the <ul> up.  The <ul> was obscuring the bottom half of the buttons on the nav bar.  Since the 
<ul> appears second in source order, it was effectively on top of the buttons - so the buttons 
were not receiving focus/clicks.  Apparently I tend to aim towards the top of the text (and 
primarily use Firefox) and my boss must be clicking towards the bottoms of the buttons.

I guess the moral of the story is that when you shoot yourself in the foot, sometimes it takes a 
while to register the pain.  :)

On Mon, 11 Jul 2005 10:22:03 -0300
  "Allard Schripsema" <allard-schripsema at procergs.rs.gov.br> wrote:
> Hi Mike,
> 
> I did see the problem. I clicked , button didn´t work,
> went to other button, went back, clicked, worked.
> Could be anything, from reusing a global variable which lost value to a bug
> in IE (I use IE 6.0.2900,2180).
> 
> I hope that diminuishing the "scope", you still can reproduce the error.
> If not, it will be hell to find the bug....
> 
> Waiting for the code,
> allard
> www.VisualDigital.com.br
> 
> -----Original Message-----
>From: javascript-bounces at LaTech.edu
> [mailto:javascript-bounces at LaTech.edu]On Behalf Of Mike Dougherty
> Sent: Monday, July 11, 2005 10:12 AM
> To: [JavaScript List]
> Subject: Re: [Javascript] Need help with IE events
> 
> 
> If I can reproduce this behavior with a simpler case, I will.  I posted this
> example just so
> someone could see the behavior.  I'm guessing the problem is in the
> complexity of attaching events
> through too many function calls.  I'll be working on it more today.
> 
> Did you at least see the problem?
> 
> On Mon, 11 Jul 2005 08:55:52 -0300
>  "Allard Schripsema" <allard-schripsema at procergs.rs.gov.br> wrote:
>> Hi Mike,
>> I´m trying to understand your code, but seriously, copying include files
>> from cache isn´t my favorite activity.
>> Can you send a simplified example of this situation so that we can see the
>> code properly instead of guessing which include  does what?