We've just upgraded from Q3 2007 to Q2 2008 to resolve the Firefox skinning issue. It now looks great in Firefox, but has brought a whole load of new issues with it as well, so for now we've reverted back to the old version.
I don't know if this bug is just local to what we've done with RadWindow, but thought I'd share it just in case. It's quite an amusing one, and one of the strangest UI bugs I've seen to date.
Try creating a RadWindow with these properties, show the modal window, wait for about 15 seconds and see what happens...
InitialBehaviours = Behaviours.Pin
Behaviours = Behaviours.None
Our other issues include no longer being able to call back to the main page and the treeview state being changed somehow between postbacks (which .net is not happy about in the slightest).
Edit - although I said it works fine in Firefox, it has actually reverted from our wonderfully crafted skin back to the default one. But hey - at least the corners work now.
I don't know if this bug is just local to what we've done with RadWindow, but thought I'd share it just in case. It's quite an amusing one, and one of the strangest UI bugs I've seen to date.
Try creating a RadWindow with these properties, show the modal window, wait for about 15 seconds and see what happens...
InitialBehaviours = Behaviours.Pin
Behaviours = Behaviours.None
Our other issues include no longer being able to call back to the main page and the treeview state being changed somehow between postbacks (which .net is not happy about in the slightest).
Edit - although I said it works fine in Firefox, it has actually reverted from our wonderfully crafted skin back to the default one. But hey - at least the corners work now.
3 Answers, 1 is accepted
0
Hello Matt,
Regarding the problem with the growing RadWindow, there is a logical error - you set pin as initial behavior and then restrict it by setting the behaviors to none.
To work around this issue, you need to set an ID for the RadWindow and then use the following style on your page:
Where WinID is the ID of RadWindow.
As for the rest of the problems, it will be best to open a support ticket and send us a small sample project that reproduces them along with reproduction details and description of the desired behavior. We will check the project and do our best to help.
Regards,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Regarding the problem with the growing RadWindow, there is a logical error - you set pin as initial behavior and then restrict it by setting the behaviors to none.
To work around this issue, you need to set an ID for the RadWindow and then use the following style on your page:
| <style type="text/css"> |
| #RadWindowWrapper_WinID .controlbuttons |
| { |
| padding: 0px !important; |
| } |
| </style> |
Where WinID is the ID of RadWindow.
As for the rest of the problems, it will be best to open a support ticket and send us a small sample project that reproduces them along with reproduction details and description of the desired behavior. We will check the project and do our best to help.
Regards,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Matt
Top achievements
Rank 1
Rank 1
answered on 07 Aug 2008, 03:10 PM
Thanks Georgi.
We actually found that simply setting both InitialBehaviors and Behaviors to None worked fine - it leads to a "pinned" modal window but without the pin button, which is what we were after.
I'll raise a support ticket for the other stuff when we come around to looking at upgrading again. For now we're sticking with the older version because it "works" and doesn't break anything else.
In the meantime we need to consider our options; re-writing our old RadWindow wrapper code or using something like the Ajax Toolkit modal window control.
Thanks again,
Matt
We actually found that simply setting both InitialBehaviors and Behaviors to None worked fine - it leads to a "pinned" modal window but without the pin button, which is what we were after.
I'll raise a support ticket for the other stuff when we come around to looking at upgrading again. For now we're sticking with the older version because it "works" and doesn't break anything else.
In the meantime we need to consider our options; re-writing our old RadWindow wrapper code or using something like the Ajax Toolkit modal window control.
Thanks again,
Matt
0
OK Matt,
We will expect your ticket regarding the other problems that you experience - we are ready to provide further assistance when needed.
Kind regards,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
We will expect your ticket regarding the other problems that you experience - we are ready to provide further assistance when needed.
Kind regards,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.