Will mark as "No Feedback" for now.

So much for that... anyway I'll probably won't have time for this 
before my vacation.
Feel free to close the ticket and I'll reopen it if ever needed in October.

I'll try to output some debug logging with alert() or console.log() tomorrow.
(I must admin I haven't done much Javascript development yet...)
to look at the actual values of my browser / window manager.

Ping?

As mentioned, 100 pixel offset is way too much.  So this needs to be 
worked around from a browser property value perspective if possible 
(i.e. detect browser that has broken window.availHeight.

This isn't correct.

screen.availHeight is defined as the available screen height taking 
into account any OS-specific UI elements.  It works fine for me: on 
FF/Win 7 screen.availHeight is the height between the top of the 
screen and the bottom taskbar.

The 50 pixels are just in there because it is difficult to move the 
window if it takes up the full screen space.  But I'd rather not be 
throwing in random pixel offsets to account for broken browser behavior.

Hi,

I really like the new window resize logic of imp.

On my desktop, the current code resizes the window so big
that the lower border of it directly sits on the taskbar.
That's makes grabbing the lower border harder than it needs to be.

I've changed the threshold value from -50 to -100 and now it looks nice.
That's also the same threshold value used in compose.js
(found while grepping for "- 100").

Cheers,
Thomas