Please describe the problem:
I moved my main panel to the bottom of the desktop. When I click on the clock applet to bring up the calendar (without the evolution appointments section expanded), about one third of the time the window pops up with its lower edge about five pixels *below* the bottom of the screen, obscuring both the last week of the month and the applet button that I need to click to close the applet.

When the appointments tab *is* expanded initially, the bottom of the calendar window is even farther below the edge of the screen, but surprisingly, the top of the window (where it says |>Appointments) is at the same place as the first case above.

In both cases, the workaround is to click the panel (to bring it above the applet), click the clock to close the applet, and click it again to reopen the applet. About two thirds of the times I click it (based on tests of repeatedly opening and closing the applet's calendar window) it works fine; one third of the time it shows this buggy behavior.

The applet shows this behavior when it is on a side or bottom panel, but not on a top panel. On a side panel it's not so crippling though, as the difference is just between a calendar rendered several pixels up or down. There is, however, no constraint in any of these cases that keeps the calendar from rendering off-screen, as in the case where a side-panel-located clock is placed near the bottom of the panel, in which case the whole thing is cut off.

Steps to reproduce:
1. Create a bottom-aligned panel.
2. Place a clock applet on that panel.
3. Open the clock applet's calendar between 1 and 5 times.


Actual results:
One of those times, the calendar is placed unusually low; sometimes so low that it goes offscreen.

Expected results:
The calendar will always be placed so that
A: All parts of the calendar are on-screen, and hence clickable.
B: The original clock applet is clickable without any explicit window-focusing onto the panel.

Does this happen every time?
About one third of the time, apparently at random, even when I attempt to reproduce the bug one time after another without changing anything about my setup.

Other information:
I will attach several screenshots.