When the wr status window does not have focus, nothing happens when you hover 
over the restbreak button. When you  click, however, you get immediately a 
restbreak.

When the wr status window does have focus, the restbreak button gets a button-
like appearance when you hover over it.

If this is ever fixed, it shall only be fixed in the Windows version.
The Gnome version shall behave like any other Gnome app, which is probably the
default behaviour you are seeing now. Consistency, please...

Just to rant a bit more. Under Linux, whether a click on an unfocused window is
actually sent to that window depends on the window manager that is running. Some
window managers do not pass on the click. In such case, it is highly indesirable
to have a border visible around the coffee cup.

I disabled the keyboard focus for the restbreak button. This removes the
"keyboard-focus-rectangle" but also prevents that pressing space activates the
restbreak....

I completely agree...

But then, for consistency's sake, if there is no border, clicking should do 
nothing, and vice versa. In all cases (including all window managers :-)

I streniously object to the actions taken at comment #3.
WR should, like any other decent Gnome 2 app, be keyboard accessible.
Accessibility is one of the major strongholds of Gnome, and you've just thrown
that away.

Yes, I already got a few restbreak windows because the mainwindow somehow got
the focus and I pressed "space". How about the BreakWindows??? I also disabled
keyboard focus of the Skip/Postpone buttons. Otherwise, you may accidentally
postpone/skip the break when you don't stop typing.

Is the pop-up menu keyboard accessible? If that could be done some how, then I
am fine with the hovering button changes...

WR is gonna be used by people who are less able. What if you've got RSI and want
to use the mouse for as little as possible? 

Or, what if you're a keyboard nut like me, who is happy that Linux finally is
keyboard accessible (like Windows has been for ages)...

For the other break windows, I do think that the skip/postpone buttons should be
somehow keyboard accessible. Random thought: create a custom widget that can
have focus, but is not visible (it renders nothing). Give focus to it when the
break window first appears. Then I can just tab to the skip/postpone buttons.

To make a long story short, this is getting off-topic... for accessibility an
other bug should be filed. But I agree that there are more important things to
do right now...

Hovering works in the linux version. The 2.0 gtk+/win32 is not as stable as the
1.2 version. Hopefully this bug will be fixed in a later gtk+/win32 version.
Perhaps I will have a look at this bug when workrave is more mature.