J
Jeremy
I've written a method that recursively loops through the control collections
on a page looking for a literal control called html.
Sometimes the html literal control will contain a child literal control
called head. Sometimes the html literal control will not have a child
literal control called head, and instead will have the head html included in
its text property. Why would asp.net sometimes parse the pages html into
literal controls and sometimes not?
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- Use doctype to force browser into standard mode. Standard mode handles
css inheritance correctly. -->
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs"
Inherits="_Default" %>
<html xmlns="http://www.w3.org/1999/xhtml">
<head><title>test</title></head>
<body>
<form id="Form1" runat="server"></form>
</body>
</html>
on a page looking for a literal control called html.
Sometimes the html literal control will contain a child literal control
called head. Sometimes the html literal control will not have a child
literal control called head, and instead will have the head html included in
its text property. Why would asp.net sometimes parse the pages html into
literal controls and sometimes not?
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- Use doctype to force browser into standard mode. Standard mode handles
css inheritance correctly. -->
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs"
Inherits="_Default" %>
<html xmlns="http://www.w3.org/1999/xhtml">
<head><title>test</title></head>
<body>
<form id="Form1" runat="server"></form>
</body>
</html>