When someone logs in to a site that I'm working on using IE (I'm using 8 and have put it into 7 mode as well) and moves the mouse pointer over different parts of the page, a mysterious blue line appears.  It's about 4-5 px thick, horizontal, and more of a dark teal shade of blue. 

[I have a screenshot of the blue line issue, but how the crud do you put one in here??  Image manager doesn't seem to work. :S]

What I believe I have narrowed it down to are the following common traits:

• It will show up directly above wherever there is a dnnTitle and lblTitle as part of the ID of the tag.

  • Example:

    • id="dnn_ctr1784_dnnTITLE_lblTitle"
    • id="dnn_ctr1590_dnnTITLE_lblTitle"
• That same tag will also always contain the function calls: _events="[object Object]" control="[object Object]"
  • *Note that these two function calls ONLY appear in IE in the generated HTML.  NEVER do they show up in FF, Chrome, or Safari
  • These calls ONLY show up after someone has logged in.
• The blue line shows up everywhere when logged in as an admin
• The blue line shows up here and there (seemingly randomly) when logged into a role other than admin
  • Sometimes the function calls show up, sometimes they don't.  So, get this, when the calls DO show up (and thus the blue line will appear when you mouse over the tag on the page containing the calls) you can F5 the page (or otherwise refresh) and the calls disappear out of the tag and the blue line doesn't show up anymore.

So, the questions:

• Does anyone know why this blue line appears?
• Why are the function calls inserted into these tages? And how are they put there?
• Why do the calls randomly show up in tags when not logged in as an admin?
• Anything else anyone can shed light on this?

1. It would be great if we could upgrade this site.  We tried and it blew up on us.  But hey, that's DNN. >:O

2. You completely misunderstood.  There are not 7 modules on the page.  I was referring to Internet Explorer being in IE7 mode.  That was to verify that the mysterious blue line issue still showed up in IE7 and that it wasn't just an IE8 problem.

3. Check physical permissions?  I guess I don't know what you're talking about. 

4. I have no reason to think that there has been any kind of attack.

Anyway, bringing it back to the function calls, somebody must know why those get injected into the generated HTML in Internet Explorer.  Any further help on that would be great.