I have problem when switch to fullscreen mode in Mushclient, I see (aprox 50 pixel height) grey field at the bottom of my screen (1024x768). I switched off buttons, statusbar, infobar, everything.
I wouldn't call it a bug though. I have the same thing whether on full screen or half screen. I just think it's part of the application border but maybe Nick can confirm if it is part of the design or an anomaly.
I don't see anything in particular at the bottom of the screen, but I do notice a thin grey line to the right of the scrollbar when both the world and MUSHclient are maximized.
Strangely enough I could reproduce a gray bar at the bottom in full-screen mode on one PC but not another.
Careful comparison has revealed that it seems to leave the gray bar (effectively, where the Windows Start bar usually is) if you have the world window *maximized* before switching to full-screen mode.
However if the world window(s) are not maximized (ie. just normal, floating around somewhere inside the main client window), then switching to full-screen uses the whole monitor area.
I still can't see what everyone else is seeing, but I noticed that if you go into fullscreen mode, then go back to normal mode, the bottom of the MUSHclient window goes below the Windows taskbar, specifically the status bar (where it says Ready).
I also notice that the full-screen mode tends to trim a few pixels off the edge of the window, like the window gets too large for the screen area. The icons at the top are slightly cut off, the text on the left is cut off about half a character, and I can barely see any of the 'Ready' text on the status bar. (EDIT: However, the RIGHT side of the window seems to have been pushed LEFT rather than too far to the right, so I can actually see the window behind MUSHclient (and click to it to switch focus)
It might be worth repeating that the world scrollbar seems to be too far left when the world and MUSHclient are both maximized (this includes fullscreen mode), revealing the grey background behind the world window. I don't know if it's part of the same issue, but it is a bit annoying.