Note that there are some explanatory texts on larger screens.

plurals
  1. POASP.NET GridView - Control Moves around in Content Page
    text
    copied!<p>I've got a project that uses a Master Page.</p> <p>There is also a Content Page that displays the summary of my data in a GridView control.</p> <p>The basics of this content element are:</p> <pre><code>&lt;table&gt; &lt;tr&gt; &lt;td&gt;Search: &lt;asp:DropDownList ID="ddlColum" runat="server"&gt;&lt;/asp:DropDownList&gt;&lt;/td&gt; &lt;td&gt;Value: &lt;asp:TextBox ID="txtValue" runat="server"&gt;&lt;/asp:TextBox&gt;&lt;/td&gt; &lt;td&gt;&lt;asp:Button ID="btnSearch" runat="server" Text="Search"&gt;&lt;/asp:Button&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td colspan="3"&gt; &lt;asp:GridView ID="summaryGrid" runat="server"&gt;&lt;/asp:GridView&gt; &lt;/td&gt; &lt;/tr&gt; &lt;/table&gt; </code></pre> <p>I have tried adding CSS to the <code>table</code>, to the <code>table row</code>, to the <code>table detail</code>, to the <code>asp:GridView</code> and to the <em>GridView</em> control's <code>CssClass</code>.</p> <p>No matter what I do, as soon as the data is bound to the <em>GridView</em> control, the control will completely fill the <code>&lt;table&gt;</code>, hiding my search controls in the first row.</p> <p>After reading up on numerous other related problems online, I thought it might be because my control does its databinding in the code behind. Therefore, I redesigned my ASP.NET page to bind in the HTML. The problem is still there, I just no longer get to initially see my search controls in the first row.</p> <p>Does anyone familiar with what would cause something like this?</p> <p><strong>EDIT:</strong></p> <p>By popular request (1 person), here's the link to the project: <a href="http://sites.google.com/site/jp2code/home/list/AcpSheetMetal.zip" rel="nofollow">>> LINK &lt;&lt;</a> (All binary information has been removed)</p> <p>Note, however, that the data binding features will not work on your end.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload