I'm not sure if this is a bug in the CSS inheritance of the latest browsers or a bug in the radFormDecorator. The button listed above displays on the screen, even though the inline style should take precedence over all other styles. I'm using a workaround of putting "display:none" in a CSS class which correctly hides the button (and prevents the radFormDecorator from rendering an anchor around the input element. I'm wondering if this is related to the "Opera hack" in the radFormDecorator's CSS file?
2 Answers, 1 is accepted
0
Georgi Tunev
Telerik team
answered on 07 Aug 2009, 07:01 AM
Hi Brent,
RadFormDecorator's
logic does not check the style property of the decorated element - this
would made the logic too complex and will lead to bad performance. When
you wish to hide such element like the button in your example, we
recommend to wrap it in some container - span or div with
style=display:none. e.g.:
Hi,
I had the same problem and I didn't want to wrap each button in another div or span.
An acceptable workaround for me was to add this jquery script in the master page
}, 4); // Wait after everything else has been done
}
);
I added a timer to allow the formdecorator some time to complete it's task. It may not be neccessary,
The only thing left is to add one style to your global css sheet.