Hello,
I recently upgraded to Telerik.Web.UI_2008_3_1327_dev_hotfix. As soon as I did this all RadWindows in Firefox "jump around" and "flash" on the screen. I made a test solution using an older Telerik.Web.UI.DLL and the RadWindow worked fine. Simply changing to the newest .DLL made the radwindow practically unusable in FireFox.
In IE it works/looks just fine.
Is this already a known issue? When can we expect a fix?
Thanks,
ethan
I recently upgraded to Telerik.Web.UI_2008_3_1327_dev_hotfix. As soon as I did this all RadWindows in Firefox "jump around" and "flash" on the screen. I made a test solution using an older Telerik.Web.UI.DLL and the RadWindow worked fine. Simply changing to the newest .DLL made the radwindow practically unusable in FireFox.
In IE it works/looks just fine.
Is this already a known issue? When can we expect a fix?
Thanks,
ethan
9 Answers, 1 is accepted
0
Hello Ethan,
The latest official version of RadControls for ASP.NET AJAX is 2008.3 1314, so I assume that you are using a custom or a nightly build. I don't know in what exact scenario you experience this problem, but if you open a support ticket and send me a small sample project, I will check it right away.
Best wishes,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
The latest official version of RadControls for ASP.NET AJAX is 2008.3 1314, so I assume that you are using a custom or a nightly build. I don't know in what exact scenario you experience this problem, but if you open a support ticket and send me a small sample project, I will check it right away.
Best wishes,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0

ethan
Top achievements
Rank 1
answered on 17 Mar 2009, 07:23 PM
I tracked this down to the InitialBehaviors ="Pin" attribute. It seems that when InitialBehaviors is set to "Pin" the rad window "jumps around" in Firefox. I changed the initial behavior to "None" and it now works.
It seems as if there is a bug with Firefox and the Pin behavior.
It seems as if there is a bug with Firefox and the Pin behavior.
0
Hello Ethan,
I tried to reproduce the problem with RadControls Q3 2008 and Q1 2009 but as you can see from the attached video, everything seems to work fine.
Could you please check my test setup below and let me know how to change it so the problem could be reproduced? I also tried using a standalone RadWindow and a RadWindow in a RadWindowManager, but I am still unable to see a problem.
Regards,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
I tried to reproduce the problem with RadControls Q3 2008 and Q1 2009 but as you can see from the attached video, everything seems to work fine.
Could you please check my test setup below and let me know how to change it so the problem could be reproduced? I also tried using a standalone RadWindow and a RadWindow in a RadWindowManager, but I am still unable to see a problem.
<form id="form1" runat="server"> |
<asp:ScriptManager ID="ScriptManager1" runat="server"> |
</asp:ScriptManager> |
<telerik:RadWindowManager ID="RadWindowManager1" runat="server"> |
<Windows> |
<telerik:RadWindow ID="RadWindow1" runat="server" NavigateUrl="http://www.google.com" |
InitialBehaviors="Pin"> |
</telerik:RadWindow> |
</Windows> |
</telerik:RadWindowManager> |
<button onclick="showWin(); return false;"> |
test</button> |
<script type="text/javascript"> |
function showWin() |
{ |
//test 1 |
//var oWnd = $find("<%= RadWindow1.ClientID %>"); |
//oWnd.show(); |
//test2 |
radopen(null,"RadWindow1"); |
} |
</script> |
</form> |
Regards,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0

ethan
Top achievements
Rank 1
answered on 19 Mar 2009, 02:49 PM
Hi Georgi,
Thanks for taking the time to look into this. I tried your example code and while I didn't see nearly the amount of flickering that I see in my code, I did still see a little. The Version of the Telerik.Web.UI dll that I am currently using in 2009.1.311.20. Here is an example of code where I am seeing a lot of "jumping around" and "flickering" of the RadWindow in Firefox (ver. 3.0.7).
<form id="form1" runat="server"> |
<telerik:RadScriptManager ID="RadScriptManager1" runat="server"/> |
<script type="text/javascript"> |
function OpenWindow() { |
radopen(null, "Window"); |
} |
</script> |
<telerik:RadWindowManager ID="WindowManager" runat="server" |
Behaviors="Close" Modal="true" Height="340px" Width="550px"> |
<Windows> |
<telerik:RadWindow ID="Window" runat="server" |
NavigateUrl="http://www.google.com" InitialBehaviors="Pin"/> |
</Windows> |
</telerik:RadWindowManager> |
<asp:Button ID="WindowButton" Text="Launch Window" runat="server" |
OnClientClick="OpenWindow();return false;" /> |
</form> |
Thanks again,
Ethan
0
Hi Ethan,
I tried your code but I still don't see a problem (see attached video). Am I missing something?
I noticed however a logical problem - in your setup you have set the InitialBehavior to Pin but the Behaviors property allows Close only. You need to allow both behaviors.
Kind regards,
Georgi Tunev
the Telerik team
Check out Telerik Trainer , the state of the art learning tool for Telerik products.
I tried your code but I still don't see a problem (see attached video). Am I missing something?
I noticed however a logical problem - in your setup you have set the InitialBehavior to Pin but the Behaviors property allows Close only. You need to allow both behaviors.
Kind regards,
Georgi Tunev
the Telerik team
Check out Telerik Trainer , the state of the art learning tool for Telerik products.
0

ethan
Top achievements
Rank 1
answered on 20 Mar 2009, 03:26 PM
Hi Georgi,
Hmm, I'm not sure why you aren't able to reproduce the flashing occurrence. When I run the sample code with the aforementioned dll, I, as well as the other developers at the company at which I work all see the flashing. There must be some other variable that is factoring in as well, but I have no idea what it could be.
As I mentioned, removing the InitialBehaviors="Pin", which, as you pointed out does not make logical sense, did fix the issue.
I appreciate you taking the time to investigate this, I'm sorry and perplexed as to why it is un-reproducable.
Thanks again,
ethan
Hmm, I'm not sure why you aren't able to reproduce the flashing occurrence. When I run the sample code with the aforementioned dll, I, as well as the other developers at the company at which I work all see the flashing. There must be some other variable that is factoring in as well, but I have no idea what it could be.
As I mentioned, removing the InitialBehaviors="Pin", which, as you pointed out does not make logical sense, did fix the issue.
I appreciate you taking the time to investigate this, I'm sorry and perplexed as to why it is un-reproducable.
Thanks again,
ethan
0

Jon
Top achievements
Rank 1
answered on 16 Mar 2011, 04:54 PM
I am also having this issue. It seems to be when both initialbehaviors="Pin" and AutoSize="true". The window starts out in the middle of the screen, but then it moves. The ending position (top left) seems to be the same x,y as when AutoSize="false". In this case, autosize=true will just about double the size of my window. This one should be easy to reproduce. Is there an order of events problem with the pinning? If you set the pin programmatically using a timeout, there is no problem.
I would really appreciate a fix :)
Thanks!
Jon Kelling
I would really appreciate a fix :)
Thanks!
Jon Kelling
0

Jon
Top achievements
Rank 1
answered on 16 Mar 2011, 04:55 PM
I am also having this issue. It seems to be when both initialbehaviors="Pin" and AutoSize="true". The window starts out in the middle of the screen, but then it moves. The ending position (top left) seems to be the same x,y as when AutoSize="false". In this case, autosize=true will just about double the size of my window. This one should be easy to reproduce. Is there an order of events problem with the pinning? If you set the pin programmatically using a timeout, there is no problem.
I would really appreciate a fix :)
Thanks!
(Sorry for the duplicate post, I just wanted to make sure a Telerik guy got the reply)
Jon Kelling
I would really appreciate a fix :)
Thanks!
(Sorry for the duplicate post, I just wanted to make sure a Telerik guy got the reply)
Jon Kelling
0
Hi Jon,
Basically, such behavior is expected, because the two actions - pinning the window and its animation, are not synchronized. If they were, i.e. we've implemented additional logic that would check for conditions like this one, this would have significantly reduce the performance because of the calculations that are needed.
What I can suggest in scenario like yours is to use the OnClientAutoSizeEnd event handler (present in Q1 2011) and to pin the RadWindow using the client-side API there.
All the best,
Georgi Tunev
the Telerik team
Basically, such behavior is expected, because the two actions - pinning the window and its animation, are not synchronized. If they were, i.e. we've implemented additional logic that would check for conditions like this one, this would have significantly reduce the performance because of the calculations that are needed.
What I can suggest in scenario like yours is to use the OnClientAutoSizeEnd event handler (present in Q1 2011) and to pin the RadWindow using the client-side API there.
All the best,
Georgi Tunev
the Telerik team