Hi Telerik,
I see all of my RadWindows sized improperly, but only when rendered under the Opera browser.
Browser Information:
Relevant code-behind:
I have attached two images to this post. They are screenshots of Chrome vs Opera for the code mentioned above. The window that I am showing in the screenshots opens up smaller than anticipated in Opera. Other RadWindows I have open larger than anticipated.
I did some searching on the Telerik forums, and found this link from 2009. I am not sure if this discussion is still applicable current day, however. If so, does Telerik have any suggestions on best practice for handling this scenario?
Cheers,
Sean
I see all of my RadWindows sized improperly, but only when rendered under the Opera browser.
Browser Information:
Version
11.51
Build
1087
Platform
Win32
System
Windows 7
XHTML+Voice
Plug-in not loaded
Browser identification
Opera/9.80 (Windows NT 6.1; U; Edition United States Local; en) Presto/2.9.168 Version/11.51
Relevant code-behind:
<
telerik:RadWindowManager
ID
=
"RadWindowManager1"
Runat
=
"Server"
Skin
=
"Web20"
Modal
=
"True"
KeepInScreenBounds
=
"True"
EnableShadow
=
"True"
Behaviors
=
"Close, Move"
VisibleStatusbar
=
"False"
ReloadOnShow
=
"True"
ShowContentDuringLoad
=
"False"
Behavior
=
"Close, Move"
Title
=
"Confirm Action"
IconUrl
=
"~/Content/Dashboard/Icons/radwindow_confirmdelete.png"
>
<
Windows
>
<
telerik:RadWindow
ID
=
"UploadDashboardWindow"
Runat
=
"Server"
NavigateUrl
=
"~/Dashboard/Dialog/Windows/UploadDashboard.aspx"
IconUrl
=
"~/Content/Dashboard/Icons/drive-upload.png"
OnClientClose
=
"OnUploadDashboardClose"
OnClientAutoSizeEnd
=
"OnClientAutoSizeEnd"
Title
=
"Upload Dashboard"
Height
=
"100"
ReloadOnShow
=
"False"
/>
</
Windows
>
</
telerik:RadWindowManager
>
<%@ Page Language="C#" EnableViewState="False" AutoEventWireup="True" CodeBehind="UploadDashboard.aspx.cs" Inherits="CableSolve.Web.Dashboard.Dialog.Windows.UploadDashboard" %>
<!DOCTYPE html>
<
html
lang
=
"en"
>
<
head
runat
=
"server"
>
<
title
></
title
>
</
head
>
<
body
>
<
form
id
=
"form1"
runat
=
"server"
>
<
link
rel
=
"stylesheet"
type
=
"text/css"
href
=
"../../../Content/Dashboard/UploadDashboard.css"
/>
<
telerik:RadCodeBlock
ID
=
"RadCodeBlock1"
Runat
=
"Server"
>
<
script
type
=
"text/javascript"
>
var radUpload1ID = "<%= RadUpload1.ClientID %>";
</
script
>
</
telerik:RadCodeBlock
>
<
telerik:RadScriptManager
ID
=
"RadScriptManager1"
Runat
=
"server"
>
<
CompositeScript
>
<
Scripts
>
<
asp:ScriptReference
Path
=
"~/Scripts/Dashboard/UploadDashboard.js"
/>
<
asp:ScriptReference
Path
=
"~/Scripts/jquery-1.4.1.min.js"
/>
</
Scripts
>
</
CompositeScript
>
</
telerik:RadScriptManager
>
<
telerik:RadFormDecorator
ID
=
"RadFormDecorator1"
Runat
=
"server"
DecoratedControls
=
"All"
Skin
=
"Web20"
/>
<
fieldset
id
=
"Upload Dashboard"
>
<
legend
>Upload Dashboard</
legend
>
<
telerik:RadUpload
ID
=
"RadUpload1"
Runat
=
"server"
AllowedFileExtensions
=
".xml"
Skin
=
"Web20"
MaxFileInputsCount
=
"1"
ControlObjectsVisibility
=
"None"
Height
=
"40px"
Width
=
"230px"
BorderWidth
=
"0px"
>
</
telerik:RadUpload
>
<
div
class
=
"BottomButton"
>
<
telerik:RadButton
ID
=
"RadButton1"
Runat
=
"server"
Skin
=
"Web20"
Text
=
"Upload"
OnClick
=
"RadButton1_Click"
OnClientClicked
=
"CloseAndSave"
/>
</
div
>
</
fieldset
>
</
form
>
</
body
>
</
html
>
html, form, body
{
font-size
:
12px
;
font-family
:
"segoe ui"
,
arial
,
sans-serif
;
overflow
:
hidden
;
}
.LabelEnabled
{
color
: Black
!important
;
}
.LabelDisabled
{
color
: Gray
!important
;
}
.riTextBox
{
color
: Black
!important
;
}
.BottomButton
{
margin-top
:
35px
;
margin-left
:
88px
;
margin-bottom
:
5px
;
}
.RadUpload .ruFileInput,
.RadUpload .ruFakeInput,
.RadUpload .ruBrowse
{
cursor
:
pointer
!important
;
}
I have attached two images to this post. They are screenshots of Chrome vs Opera for the code mentioned above. The window that I am showing in the screenshots opens up smaller than anticipated in Opera. Other RadWindows I have open larger than anticipated.
I did some searching on the Telerik forums, and found this link from 2009. I am not sure if this discussion is still applicable current day, however. If so, does Telerik have any suggestions on best practice for handling this scenario?
Cheers,
Sean