In the out-of-the-box skins, RadToolBarItems have a different look when focused. The focus effect stays in place until the user moves focus to another element in the page. There are quite a few cases where this is undesirable and the button should revert to its normal look as soon as the click is complete.
Overriding the styles has limitations, and seems like it could cause issues when the control is upgraded in the future. You end up overriding all sorts of classes like .rtbIn, .rtbWrap, .rtbMid, etc.
The FocusedCssClass property seemed like a good solution, but it used to supplement rather than override the default focused class.
As an interim solution, I simply call focus() then blur() on a different ToolBarItem (or any visible form element). This works like a charm, but I'd rather not use such a hack.
I guess I'd like to know why the focused buttons behave the way they do in the default skins. It makes them feel more like toggle buttons and winds up confusing the user. It feels great that the buttons "light-up" when you click on them, but keeping them lit up until focus is lost feels unnatural and serves little purpose.
Overriding the styles has limitations, and seems like it could cause issues when the control is upgraded in the future. You end up overriding all sorts of classes like .rtbIn, .rtbWrap, .rtbMid, etc.
The FocusedCssClass property seemed like a good solution, but it used to supplement rather than override the default focused class.
As an interim solution, I simply call focus() then blur() on a different ToolBarItem (or any visible form element). This works like a charm, but I'd rather not use such a hack.
I guess I'd like to know why the focused buttons behave the way they do in the default skins. It makes them feel more like toggle buttons and winds up confusing the user. It feels great that the buttons "light-up" when you click on them, but keeping them lit up until focus is lost feels unnatural and serves little purpose.