Very annoying IE7 ​behaviour/b​ug...

IE7 focuses own windows when page loading is finished. So annoying if you have several applications running in same time.


Does MS/IE planning to fix this issue?


Second bughaviour related to tabs. When you closing tabs using middle mouse button IE closes tab using "MouseButtonDown" event, instead of "MouseButtonUp". In same time closing tabs by tab's "close"  button works from "MouseUp"/"MouseClick" event. It's very annoying too. Sometimes user can change mind in last moment, even if button is already pressed. User just need to move mose somewhere and release button. It's impossible for middle button click, because tabs is already closed. When I've reported about this to MS then gave me extremely stupid answer "We are very sorry what you're expreiencing problems with IE"...

Does MS planning to incliude this bughaviours in IE8?

BlackTiger wrote:

IE7 focuses own windows when page loading in finished. So annoying if you have several applications running in same time.

CannotResolveSymbol wrote:



BlackTiger wrote: IE7 focuses own windows when page loading in finished. So annoying if you have several applications running in same time.

Never seen this one.

BlackTiger wrote:

IE7 focuses own windows when page loading is finished. So annoying if you have several applications running in same time.


Does MS/IE planning to fix this issue?


Second bughaviour related to tabs. When you closing tabs using middle mouse button IE closes tab using "MouseButtonDown" event, instead of "MouseButtonUp". In same time closing tabs by tab's "close"  button works from "MouseUp"/"MouseClick" event. It's very annoying too. Sometimes user can change mind in last moment, even if button is already pressed. User just need to move mose somewhere and release button. It's impossible for middle button click, because tabs is already closed. When I've reported about this to MS then gave me extremely stupid answer "We are very sorry what you're expreiencing problems with IE"...

Does MS planning to incliude this bughaviours in IE8?

We obey the same rules as every Win32 app when it comes to focus. There's a set of rules published on MSDN on how setforegroundwindow is supposed to behave.

The only thing that comes to mind is if you have IE under the debugger. Then it gets a free pass everytime we call SetForegroundWindow. So you lose your debugger focus, but that's really a windows issue.

I'll be on the lookout for any instances where this happens though. If you have a solid repro on multiple non-dev (near clean installs) boxes please let me know.

The middle button is a strange situation. The change tab left click is a down event, but the close button is a left click up event. Perhaps the close should be a middle click up. (Or maybe the close button should be a down event )

Bloody hell!!! [6]

I've made some investigations... Bloody JavaScript!

It was a call of "window.focus();" funtion in page's script... That why it happening only on some sites...

Sometimes I hate JS...

BlackTiger wrote:

Bloody hell!!!

I've made some investigations... Bloody JavaScript!

It was a call of "window.focus();" funtion in page's script... That why it happening only on some sites...

Sometimes I hate JS...

BlackTiger wrote:

Bloody hell!!!

I've made some investigations... Bloody JavaScript!

It was a call of "window.focus();" funtion in page's script... That why it happening only on some sites...

Sometimes I hate JS...

The middle click bug is happening for me

CannotResolveSymbol wrote:



BlackTiger wrote:Bloody hell!!! I've made some investigations... Bloody JavaScript! It was a call of "window.focus();" funtion in page's script... That why it happening only on some sites... Sometimes I hate JS...

I think someone should "investigate" more thoroughly before coming on here and whining about how everything's Microsoft's fault...

I can report that the focus bug happens with me as well. It is very annoying since I might be typing something in another application and IE steals the focus away. It doesn't exactly steal the focus in my case but it removes rather the focus from the application that has the focus but does not place it in IE itself. I don't know if this is a JavaScript or IE bug, I don't know if this is a Windows bug but it doesn't happen with any other application such as Windows Live Messenger. I have not changed my registry settings myself.
The question, however, remains: Even if it is Windows fault or perhaps my own settings for focus handling, why does IE in any case need to call the SetForegroundWindow function? Does it call the function after it loads a page? And if so, why? It didn't happen with IE6. Was the behaviour changed in IE7 to set the focus after it loads a page, even if this is done through the "polite" Windows SetForegroundWindow function? If yes, please remove this behaviour as it has annoyed me many times.
Please also look for and fix another potential bug in IE and in Windows Media Player where the alt key does not only close a pop-up context menu, as in all other Windows applications, but it also brings up the application main menu at the same time.

I'm currently working on a system that uses quite a lot of popups and have encountered with this issue, I present an oversimplified example.

The file popup.html conatains:

<html>
  <head>
    <script language='javascript'>
      window.onload = function (){ window.document.getElementById('inputThing').focus(); };
      function popup(){
        var newWindow = window.open('popup.html','','width=200,height=200');
      }
    </script>
  </head>
  <body>
    <a href='popup.html' onclick="popup();">Click Me</a>
    <input id='inputThing' type='text'></input>
  </body>
</html>


In FF and IE 6 or lower, clicking on the link opens the popup, relocates the main window, and gives focus to the popup.
On IE 7, however (because of the focus event launched onload in the newly-opened main window), after the main page loads the focus is taken from the popup and given to the main window.