Hi,
Howard Lewis Ship wrote on Sat, 24 Mar 2007 11:42:22 -0800
This is correct behavior for rendering HTML (as opposed to XHTML).
Unlike T4, T5 knows the difference. HTML is a SGML language where
open tags are not necessarly balanced with close tags.
What's coming is the ability for
Just hasn't been fleshed out yet; there needs to be a negotiation between
the MarkupWriterFactory service and the page that does the rendering to
determine the correct MarkupWriter configuration for the result.
On 5/29/07, Martin Dietze [EMAIL PROTECTED] wrote:
Hi,
Howard Lewis Ship wrote on
On Tue, May 29, 2007, Howard Lewis Ship wrote:
Just hasn't been fleshed out yet; there needs to be a negotiation between
the MarkupWriterFactory service and the page that does the rendering to
determine the correct MarkupWriter configuration for the result.
sorry, -v, please :)
Cheers,
On Tue, May 29, 2007, Martin Dietze wrote:
On Tue, May 29, 2007, Howard Lewis Ship wrote:
Just hasn't been fleshed out yet; there needs to be a negotiation between
the MarkupWriterFactory service and the page that does the rendering to
determine the correct MarkupWriter configuration for
This is correct behavior for rendering HTML (as opposed to XHTML).
Unlike T4, T5 knows the difference. HTML is a SGML language where
open tags are not necessarly balanced with close tags.
What's coming is the ability for Tapestry to render XML/XHTML
correctly and choose the correct strategy
