Mounir Maghraoui
Top achievements
Rank 1
Rank 1
Mounir Maghraoui
asked on 16 Mar 2010, 05:29 PM
Hi,
I'm using Telerik version 2009.31208.20. I have created an asp:button decorated with the Telerik RadFormDecorator. The button works well in IE (all version after IE 6), FireFox 3.x, Chrome and Safari. Although, in Firefox 2.x, the button click is not firing and its border is cut off.
The problem occurs only when i set the button decorated with the RadFormDecorator.
I found the same problem in the Telerik website http://demos.telerik.com/aspnet-ajax/formdecorator/examples/decorationzoneid/defaultcs.aspx. I have joined to this post a snapshot from the Telerik website.
Thanks.
here the source code:
I'm using Telerik version 2009.31208.20. I have created an asp:button decorated with the Telerik RadFormDecorator. The button works well in IE (all version after IE 6), FireFox 3.x, Chrome and Safari. Although, in Firefox 2.x, the button click is not firing and its border is cut off.
The problem occurs only when i set the button decorated with the RadFormDecorator.
I found the same problem in the Telerik website http://demos.telerik.com/aspnet-ajax/formdecorator/examples/decorationzoneid/defaultcs.aspx. I have joined to this post a snapshot from the Telerik website.
Thanks.
here the source code:
| <telerik:RadFormDecorator ID="FormDecorator1" runat="server" DecoratedControls="All" | |
| Skin="WebBlue"></telerik:RadFormDecorator> | |
| <asp:Button ID="LoginButton" ValidationGroup="login" | |
| runat="server" CommandName="Login" Width="120px" | |
| Text="<%$ Resources:Labels, LoginLoginButton %>" /> |
7 Answers, 1 is accepted
0
Accepted
Hi Mounir,
Try setting UseSubmitBehavior=false for the button - it should help when FF2 is used.
Regards,
Georgi Tunev
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Try setting UseSubmitBehavior=false for the button - it should help when FF2 is used.
Regards,
Georgi Tunev
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
Mounir Maghraoui
Top achievements
Rank 1
Rank 1
answered on 19 Mar 2010, 02:36 PM
Hi Georgi,
Your suggestion of setting UseSubmitBehavior=false for the button works well. Thank you for help!
Now, still the button border cut off as in the attached file.
Is there a way to fix it ?
kind regards,
Mounir
Your suggestion of setting UseSubmitBehavior=false for the button works well. Thank you for help!
Now, still the button border cut off as in the attached file.
Is there a way to fix it ?
kind regards,
Mounir
0
Accepted
Hi Mounir,
We are aware of this problem. It is caused by the lack of support for the display: inline-block CSS property / value in that version of FireFox. When FF3 was released, they implemented this mode (which is in fact a standard CSS2 value), which allowed us to drop a couple of vendor-specific (-moz-properties) that we used to emulate this behavior. What you can do is to set the following CSS:
.rfdSkinnedButton
{
display: block !important;
float: left !important;
}
However, have in mind that this may affect your layout because of the float, i.e - if you have a <div /> after the button it will stand next to it, not below it. To fix this, use <br style="clear: both;" /> or apply clear: both; to the <div /> itself.
Unfortunately, there are no browser hacks for FF and I cannot give you a solution that will execute only in FF < 3 versions. On the other hand we do not plan reverting to the -moz properties, as they are hard to maintain and cause other problems.
Regards,
Georgi Tunev
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
We are aware of this problem. It is caused by the lack of support for the display: inline-block CSS property / value in that version of FireFox. When FF3 was released, they implemented this mode (which is in fact a standard CSS2 value), which allowed us to drop a couple of vendor-specific (-moz-properties) that we used to emulate this behavior. What you can do is to set the following CSS:
.rfdSkinnedButton
{
display: block !important;
float: left !important;
}
However, have in mind that this may affect your layout because of the float, i.e - if you have a <div /> after the button it will stand next to it, not below it. To fix this, use <br style="clear: both;" /> or apply clear: both; to the <div /> itself.
Unfortunately, there are no browser hacks for FF and I cannot give you a solution that will execute only in FF < 3 versions. On the other hand we do not plan reverting to the -moz properties, as they are hard to maintain and cause other problems.
Regards,
Georgi Tunev
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
Djakhongir Makhkamov
Top achievements
Rank 1
Rank 1
answered on 18 May 2010, 12:40 PM
<"Try setting UseSubmitBehavior=false for the button - it should help when FF2 is used. ">
But how to implement this to all buttons at once?0
Hello,
The easiest way to do it is a global find & replace operation in your VS project (Ctrl+Shift+H). Find all "<asp:Button" and replace them with "<asp:Button UseSubmitBehavior=false".
If your project has a base page class, you can write a small recursive method that crawls the page controls and if it finds a Button control, sets the property. However, this must be done before the OnPreRender event of the button, because the button control uses the UseSubmitBehavior value after that.
All the best,
Lini
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
The easiest way to do it is a global find & replace operation in your VS project (Ctrl+Shift+H). Find all "<asp:Button" and replace them with "<asp:Button UseSubmitBehavior=false".
If your project has a base page class, you can write a small recursive method that crawls the page controls and if it finds a Button control, sets the property. However, this must be done before the OnPreRender event of the button, because the button control uses the UseSubmitBehavior value after that.
All the best,
Lini
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
Djakhongir Makhkamov
Top achievements
Rank 1
Rank 1
answered on 21 May 2010, 06:10 PM
Thanks a lot.
however, is there a way to do so, that whenever i drag and drop a button, this property will be set?
0
Hi,
No - we have no control over the markup, that is generated when you drop a button from the Visual Studio toolbox. Unfortunately, the only workaround is to manually set the property after the button has been added.
Kind regards,
Lini
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
No - we have no control over the markup, that is generated when you drop a button from the Visual Studio toolbox. Unfortunately, the only workaround is to manually set the property after the button has been added.
Kind regards,
Lini
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.