Talk:HTML vs. XHTML - Revision history

Brettz9: /* Harmony */

2010-03-18T03:38:36Z

Harmony

← Older revision		Revision as of 03:38, 18 March 2010
Line 130:		Line 130:
	Hi,		Hi,

	Was just wondering whether the page could be structured such that differences were categorized in such a way to allow HTML authors to know how to craft documents in such a way as to be compatible with XHTML (e.g., properly nesting), and XHTML authors to know how to craft documents to be maximally compatible with HTML (e.g., don't use CDATA sections)? I would think this could be done non-redundantly, such as by grouping those belonging to the same category together, or at least color-coding such entries. Maybe a special column could be added for such compatibility guidelines (but again, distinguishing the directionality of the compatibility)? I'd also hope that such compatibility info ''could'' take into account HTML4/legacy browsers in order to be fully practical...		Was just wondering whether the page could be structured such that differences were categorized in such a way to allow HTML authors to know how to craft documents in such a way as to be compatible with XHTML (e.g., properly nesting), and XHTML authors to know how to craft documents to be maximally compatible with HTML (e.g., don't use CDATA sections)? I would think this could be done non-redundantly, such as by grouping those belonging to the same category together, or at least color-coding such entries. Maybe a special column could be added for such compatibility guidelines (but again, distinguishing the directionality of the compatibility)? I'd also hope that such compatibility info ''could'' take into account HTML4/legacy browsers in order to be fully practical...

			I suggest this because it could better inform the HTML5 editing decision-making (e.g., aspects of better XML compatibility to consider now or in future editions of HTML, if transitional deprecating is no longer to be practiced) as well as comprehensively address the compatibility issues as nowhere else addresses (nor is likely to address without such as the expertise of the contributors here).

	Also, are the items following the table in the "Syntax and Parsing" supposed to be integrated into the table or what?		Also, are the items following the table in the "Syntax and Parsing" supposed to be integrated into the table or what?

	[[User:Brettz9\|Brettz9]] 02:56, 18 March 2010 (UTC)		[[User:Brettz9\|Brettz9]] 02:56, 18 March 2010 (UTC)

Brettz9: /* Harmony */

2010-03-18T03:03:39Z

Harmony

← Older revision		Revision as of 03:03, 18 March 2010
Line 130:		Line 130:
	Hi,		Hi,

	Was just wondering whether the page could be structured such that differences were categorized in such a way to allow HTML authors to know how to craft documents in such a way as to be compatible with XHTML (e.g., properly nesting), and XHTML authors to know how to craft documents to be maximally compatible with HTML (e.g., don't use CDATA sections)? I would think this could be done non-redundantly, such as by grouping those belonging to the same category together, or at least color-coding such entries. Maybe a special column could be added for such compatibility guidelines (but again, distinguishing the directionality of the compatibility)?		Was just wondering whether the page could be structured such that differences were categorized in such a way to allow HTML authors to know how to craft documents in such a way as to be compatible with XHTML (e.g., properly nesting), and XHTML authors to know how to craft documents to be maximally compatible with HTML (e.g., don't use CDATA sections)? I would think this could be done non-redundantly, such as by grouping those belonging to the same category together, or at least color-coding such entries. Maybe a special column could be added for such compatibility guidelines (but again, distinguishing the directionality of the compatibility)? I'd also hope that such compatibility info ''could'' take into account HTML4/legacy browsers in order to be fully practical...

	Also, are the items following the table in the "Syntax and Parsing" supposed to be integrated into the table or what?		Also, are the items following the table in the "Syntax and Parsing" supposed to be integrated into the table or what?

	[[User:Brettz9\|Brettz9]] 02:56, 18 March 2010 (UTC)		[[User:Brettz9\|Brettz9]] 02:56, 18 March 2010 (UTC)

Brettz9: /* Harmony */

2010-03-18T02:59:25Z

Harmony

← Older revision		Revision as of 02:59, 18 March 2010
Line 130:		Line 130:
	Hi,		Hi,

	Was just wondering whether the page could be structured such that differences were categorized in such a way to allow HTML authors to know how to craft documents in such a way as to be compatible with XHTML (e.g., properly nesting), and XHTML authors to know how to craft documents to be maximally compatible with HTML (e.g., don't use CDATA sections)? I would think this could be done non-redundantly, such as by grouping those belonging to the same category together, or at least color-coding such entries.		Was just wondering whether the page could be structured such that differences were categorized in such a way to allow HTML authors to know how to craft documents in such a way as to be compatible with XHTML (e.g., properly nesting), and XHTML authors to know how to craft documents to be maximally compatible with HTML (e.g., don't use CDATA sections)? I would think this could be done non-redundantly, such as by grouping those belonging to the same category together, or at least color-coding such entries. Maybe a special column could be added for such compatibility guidelines (but again, distinguishing the directionality of the compatibility)?

	Also, are the items following the table in the "Syntax and Parsing" supposed to be integrated into the table or what?		Also, are the items following the table in the "Syntax and Parsing" supposed to be integrated into the table or what?

	[[User:Brettz9\|Brettz9]] 02:56, 18 March 2010 (UTC)		[[User:Brettz9\|Brettz9]] 02:56, 18 March 2010 (UTC)

Brettz9: /* Harmony */ new section

2010-03-18T02:56:40Z

Harmony: new section

← Older revision		Revision as of 02:56, 18 March 2010
Line 125:		Line 125:
	</pre>		</pre>
	:You can verify this in Firebug or DOM Inspector. --[[User:ThomasR\|ThomasR]] 04:34, 23 March 2009 (UTC)		:You can verify this in Firebug or DOM Inspector. --[[User:ThomasR\|ThomasR]] 04:34, 23 March 2009 (UTC)

			== Harmony ==

			Hi,

			Was just wondering whether the page could be structured such that differences were categorized in such a way to allow HTML authors to know how to craft documents in such a way as to be compatible with XHTML (e.g., properly nesting), and XHTML authors to know how to craft documents to be maximally compatible with HTML (e.g., don't use CDATA sections)? I would think this could be done non-redundantly, such as by grouping those belonging to the same category together, or at least color-coding such entries.

			Also, are the items following the table in the "Syntax and Parsing" supposed to be integrated into the table or what?

			[[User:Brettz9\|Brettz9]] 02:56, 18 March 2010 (UTC)

ThomasR: /* table cannot have tr child? */

2009-03-25T22:25:36Z

table cannot have tr child?

← Older revision		Revision as of 22:25, 25 March 2009
Line 113:		Line 113:
	</pre>		</pre>

	:The [http://www.w3.org/TR/html401/sgml/dtd.html HTML DTD] specifies that the <code>TABLE</code> element can only contain <code>CAPTION, COL, COLGROUP, THEAD TFOOT</code> and <code>TBODY</code>. However, both start and end tags of <code>TBODY</code> are optional, so your ~~example generates the same DOM tree as this~~:		: - Note that ''tag'' ≠ ''element''. The [http://www.w3.org/TR/html401/sgml/dtd.html HTML 4.01 DTD] specifies that the <code>TABLE</code> element can only contain <code>CAPTION, COL, COLGROUP, THEAD TFOOT</code> and <code>TBODY</code>. However, both start and end tags of <code>TBODY</code> are optional, so your <code>TR</code>s are actually not children of <code>TABLE</code>, but children of an "invisible" <code>TBODY</code> element:
	<pre>		<pre>
	<table>		<table>
	<tbody>		<tbody><!-- this line is optional in HTML -->
	<tr>		<tr>
	<td></td>		<td></td>
	<td></td>		<td></td>
	</tr>		</tr>
	</tbody>		</tbody><!-- this line is optional in HTML -->
	</table>		</table>
	</pre>		</pre>
	:You can verify this in Firebug or DOM Inspector. --[[User:ThomasR\|ThomasR]] 04:34, 23 March 2009 (UTC)		:You can verify this in Firebug or DOM Inspector. --[[User:ThomasR\|ThomasR]] 04:34, 23 March 2009 (UTC)

ThomasR: /* table cannot have tr child? */

2009-03-23T04:34:12Z

table cannot have tr child?

← Older revision		Revision as of 04:34, 23 March 2009
Line 112:		Line 112:

	</pre>		</pre>

			:The [http://www.w3.org/TR/html401/sgml/dtd.html HTML DTD] specifies that the <code>TABLE</code> element can only contain <code>CAPTION, COL, COLGROUP, THEAD TFOOT</code> and <code>TBODY</code>. However, both start and end tags of <code>TBODY</code> are optional, so your example generates the same DOM tree as this:
			<pre>
			<table>
			<tbody>
			<tr>
			<td></td>
			<td></td>
			</tr>
			</tbody>
			</table>
			</pre>
			:You can verify this in Firebug or DOM Inspector. --[[User:ThomasR\|ThomasR]] 04:34, 23 March 2009 (UTC)

Philip Taylor: revert spam

2008-03-21T18:57:57Z

revert spam

← Older revision		Revision as of 18:57, 21 March 2008
Line 112:		Line 112:

	</pre>		</pre>

	~~== booktrailer on youtube ==~~

	What an interesting way to get people interested in reading! Book trailers are like movie trailers, but for books! You can find them all over the internet now, but here is a site that's featuring them on YouTube. http://www.youtube.com/booktrailers

	~~== booktrailer on youtube ==~~

	What an interesting way to get people interested in reading! Book trailers are like movie trailers, but for books! You can find them all over the internet now, but here is a site that's featuring them on YouTube. http://www.youtube.com/booktrailers

Mpsingh: New section: booktrailer on youtube

2008-03-21T17:35:10Z

New section: booktrailer on youtube

← Older revision		Revision as of 17:35, 21 March 2008
Line 112:		Line 112:

	</pre>		</pre>

			== booktrailer on youtube ==

			What an interesting way to get people interested in reading! Book trailers are like movie trailers, but for books! You can find them all over the internet now, but here is a site that's featuring them on YouTube. http://www.youtube.com/booktrailers

	== booktrailer on youtube ==		== booktrailer on youtube ==

	What an interesting way to get people interested in reading! Book trailers are like movie trailers, but for books! You can find them all over the internet now, but here is a site that's featuring them on YouTube. http://www.youtube.com/booktrailers		What an interesting way to get people interested in reading! Book trailers are like movie trailers, but for books! You can find them all over the internet now, but here is a site that's featuring them on YouTube. http://www.youtube.com/booktrailers

Mpsingh: New section: booktrailer on youtube

2008-03-21T17:34:58Z

New section: booktrailer on youtube

← Older revision		Revision as of 17:34, 21 March 2008
Line 112:		Line 112:

	</pre>		</pre>

			== booktrailer on youtube ==

			What an interesting way to get people interested in reading! Book trailers are like movie trailers, but for books! You can find them all over the internet now, but here is a site that's featuring them on YouTube. http://www.youtube.com/booktrailers

Combatentropy: /* table inside p? */

2007-06-27T16:43:08Z

table inside p?

← Older revision		Revision as of 16:43, 27 June 2007
Line 91:		Line 91:

	All of those elements listed are defined to be allowed where strcutred inline-level content is allowed. This is a change from HTML 4.01 and XHTML 1.0, and is similar to model proposed in XHTML 2.0. -- [[User:Lachlan Hunt\|Lachlan Hunt]] 13:39, 5 December 2006 (UTC)		All of those elements listed are defined to be allowed where strcutred inline-level content is allowed. This is a change from HTML 4.01 and XHTML 1.0, and is similar to model proposed in XHTML 2.0. -- [[User:Lachlan Hunt\|Lachlan Hunt]] 13:39, 5 December 2006 (UTC)

			=== table cannot have tr child? ===

			Do you really mean the following:

			<blockquote>
			In XHTML, table elements may contain child tr elements. In the HTML serialisation, due to backwards compatibility constraints, this is not possible (though it may be done through DOM manipulation).
			</blockquote>

			So, in HTML, is this not possible?

			<pre>

			<table>
			<tr>
			<td></td>
			<td></td>
			</tr>
			</table>

			</pre>