[
https://issues.apache.org/jira/browse/TAPESTRY-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557400#action_12557400
]
nirvdrum edited comment on TAPESTRY-2028 at 1/9/08 11:50 AM:
-----------------------------------------------------------------
What actually prompted this? I don't require the whitespace for rendering
anywhere (at least that I know of -- this isn't going to be a fun way to find
out), but just about any other debugging issue is going to be terrible.
Looking at the source before it's processed doesn't always help because one may
not know how any components or their IDs will render until they do so.
I can empathize with the performance of the parser, but this really seems to be
too invasive of an operation for a framework to be performing. As for client
speed, the whitespace issue was solved a long time ago via gzip compression.
I'd rather see Tapestry include a gzip filter that's enabled by default than
this approach.
was (Author: nirvdrum):
What actually prompted this? I don't require the whitespace for rendering
anywhere (at that I know of -- this isn't going to be a fun way to find out),
but just about any other debugging issue is going to be terrible. Looking at
the source before its processed doesn't always help because one may not know
how any components or their IDs will render until they do so.
I can empathize with the performance of the parser, but this really seems to be
too invasive of an operation for a framework to be performing. As for client
speed, the whitespace issue was solved a long time ago via gzip compression.
I'd rather see Tapestry include a gzip filter that's enabled by default than
this approach.
> 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]
