[
https://issues.apache.org/jira/browse/TAPESTRY-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557405#action_12557405
]
Howard M. Lewis Ship commented on TAPESTRY-2028:
------------------------------------------------
I think there's an existing issue to include GZIP filtering.
This has been a complaint I've received from clients going a ways back.
It actually does affect server-side performance (though I'm at a loss as to how
to measure it). Basically, there are a lot fewer tokens in the parsed
templates, since many whitespace-only text tokens drop out ... that means fewer
nodes in the rendered DOM and less work to convert that to an output stream.
> Mimimize whitespace in the output markup
> ----------------------------------------
>
> Key: TAPESTRY-2028
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2028
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.7
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.8
>
>
> Tapestry (4 and 5) has traditionally honored all the white space in a
> template. This is for a few specific cases, such as text inside a <pre>
> element (who uses those?).
> This results in output documents that, due to the extra whitespace that often
> surrounds Tapestry components, contain large amounts of whitespace.
> In most cases, interior white space (whitespace between text characters) can
> be reduced to a single space, and white space just after a tag or just before
> a tag can be eliminated entirely.
> The Tapestry template parser should honor the xml:space attribute and use it
> to determine what template whitespace is relevant, and what whitespace may be
> minimized or eliminated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
