PDA

View Full Version : [CLOSED] [#12] Border set to false breaks the rendering of child controls



RCN
Oct 16, 2012, 1:46 PM
Hi folks, when i have a Panel (_pnlRoot) with the Border property set to false and _pnlRoot has a child Panel (_pnlSub) with a TopBar, the header of _pnlSub does not render properly.



<ext:Panel ID="_pnlRoot" Title="Ext" Border="false" runat="server">
<Items>
<ext:Panel ID="_pnlSub" Title="Net" runat="server">
<TopBar>
<ext:Toolbar ID="Toolbar2" runat="server">
<Items>
<ext:Button ID="Button7" runat="server" Text="Ext" />
<ext:ToolbarFill />
<ext:Button ID="Button1" runat="server" Text="Net" />
</Items>
</ext:Toolbar>
</TopBar>
</ext:Panel>
</Items>
</ext:Panel>


Any ideas to overcome this issue?

Thanks in advance

geoffrey.mcgill
Oct 16, 2012, 2:47 PM
Yes, there does appear to be a problem when Border="false". We will investigate.

Here's a complete .aspx code sample demonstrating the whole scenario, which can be copy/paste directly into a local project.

Example


<%@ Page Language="C#" %>
<!DOCTYPE html>

<html>
<head runat="server">
<title>Ext.NET Example</title>
</head>
<body>
<ext:ResourceManager runat="server" />

<ext:Panel runat="server" Title="Parent" Border="false">
<Items>
<ext:Panel runat="server" Title="Child">
<TopBar>
<ext:Toolbar runat="server">
<Items>
<ext:Button runat="server" Text="Left" />
<ext:ToolbarFill runat="server" />
<ext:Button runat="server" Text="Right" />
</Items>
</ext:Toolbar>
</TopBar>
</ext:Panel>
</Items>
</ext:Panel>
</body>
</html>

RCN
Oct 16, 2012, 4:04 PM
Please keep me posted.

Daniil
Oct 16, 2012, 5:41 PM
I reported to Sencha.
http://www.sencha.com/forum/showthread.php?246224

RCN
Oct 16, 2012, 6:25 PM
Thank you Danill

Daniil
Oct 17, 2012, 4:53 AM
Sencha fixed it in 4.1.3. So, the fix will appear in Ext.NET after updating ExtJS. No time frame yet, because no time frame for ExtJS 4.1.3 release.

RCN
Oct 17, 2012, 11:50 AM
Ok, please keep me posted

geoffrey.mcgill
Nov 16, 2012, 5:22 AM
Opened an Issue on GitHub to track this defect, see

https://github.com/extnet/Ext.NET/issues/12

Looks like this issue has been fixed in Ext JS 4.2. The fix will be incorporated in the Ext.NET 2.2 release.

Daniil
Dec 29, 2012, 11:02 AM
The issue has been fixed in SVN.

Thank you again for the report.