Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1041295
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T15:19:52+00:00 2026-05-16T15:19:52+00:00

Let me just first point out to any IE users right now (this is

  • 0

Let me just first point out to any IE users right now (this is not a problem in Chrome, Safari or Firefox) hint hint 😉

So… I have a issue with my tooltips in IE, I have a onmouseover listener for all the elements which are to be hoverable and then in my mouseover function I have a very basic cross browser declaration as such…

var event = e || window.event,
    el = event.target || event.srcElement;

I’ve been having issues with the window object not existing in IE or something, this has been a issue after I added a flag to ignore mouseover’s from one element mouseover on the way to the tooltip itself (during the time cycle allowed, 300ms). In other words the flag is to ignore mouseovers on route to the tooltip from the original mouseover.

So that logic looks like this…

loadtip.refMouseOver = function (e) {

    var event = e || window.event, el = event.target || event.srcElement;
    //console.log(window); // <-- throws error in IE (Member not found)
    // Reset the lastHoveredRef data.
    tipManager.lastHoveredRef = null;
    tipManager.lastHoveredRef = [el, event];

    // true means there is a tip open still, so if no tip is open.
    if (tipManager.tipState !== true) { 
        tipManager.processTip(el, event);
    } else {        
        return; // do nothing
    }

}

The "Member not found" error will occur when I hover from one element quickly to the next in IE with the tooltip still open.

I read about window.open and close stuff with a try catch but I didn’t see how that was relevant. Any help is greatly appreciated.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T15:19:53+00:00Added an answer on May 16, 2026 at 3:19 pm

    Ok I have found the problem.

    To sum it up, basically IE will not pass a event to another function if that function call is within a setTimeout.

    So you can trick IE by creating a copy of the event and passing that, here is a example of that…

    var eventCopy = {};
    for (var i in event) {
        eventCopy[i] = event[i];    
    }
    

    Then just send your function the eventCopy, even though this is a ‘total’ hack.

    setTimeout(function () { yourFunction(eventCopy), yourDelayTime);
    

    And voila it will work.

    I should add, that Internet Explorer will merely create a reference to the global window event which is why we need the copy of event. This is because by the time setTimeout calls the function, windows.event has already passed,

    Bottom line… don’t try to send a event inside a setTimeout because IE won’t accept it. This is true for IE 6, 7 & 8 from my testing.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

First, let me just say that I have searched for information on this topic;
Let me first put the code snippets here. I am just using the ASP.NET
In my project I need to write small WYSIWYG editor (just let users make
I've been having this bothering recurring theme; let's just say, I have a class
First and foremost, apologies for any cross-posting. Hope I'm not repeating an issue here,
I am not sure whether this is just a simple mistake of my code.
Let me start out by saying I have tried this and looked at this
I'm not new to this technology, but one thing is bugging me out. It's
Let's just say that I need to render a certain amount of HTML over
I am trying to build a Quadtree data structure(or let's just say a tree)

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.