When foobar is the last application to be minimized to the systray, a left mouse button release anywhere in the systray raises foobar.
This does not happen when other applications were minimized to the systray after foobar.

To reproduce this:
- raise then minimise foobar to the systray
- press the left mouse button in any empty space of the taskbar
- move your mouse in the systray, not necessarily on the foobar icon
- release the button

Expected behaviour: foobar should raise only when you click on the systray icon

An alternate solution is to only catch WM_*BUTTONUP preceded by WM_*BUTTONDOWN, which is only sent when the icon itself is clicked. WM_*BUTTONUP is always sent after direct clicks, so it should follow that a status variable set by button down will always be cleared properly, and if popup is only triggered by button up when that variable is set, we well get clicks when we want them.

It should also follow that double click triggered events should set a variable on double click and activate on button up if that variable is set. Doing it this way would also eliminate false button up triggers on icons that do not already check for preceding button down or double click.

I should start collecting information like this on a web page, or find a nice wiki or something.

Eh, whatever.

What kode just said totally went over my head but er... reproduced.

Reproduced.

This will probably be corrected, but I was just stating some general information for anyone else who is developing any software that uses a notification icon. ui_columns has this same problem. A number of programs pop up on button down, which I find to be annoying.

Wow, what a surprise, the network connection status icon in Windows XP SP1 has the same problem as well. It appears to affect whichever icon is currently focused, unless the software has the workaround I described above.