You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/06/18 23:16:07 UTC
[jira] Created: (TAP5-751) Add a development mode option that emits
extra comments to identify which comments are responsible for which
portions of the rendered markup
Add a development mode option that emits extra comments to identify which comments are responsible for which portions of the rendered markup
--------------------------------------------------------------------------------------------------------------------------------------------
Key: TAP5-751
URL: https://issues.apache.org/jira/browse/TAP5-751
Project: Tapestry 5
Issue Type: New Feature
Components: tapestry-core
Affects Versions: 5.2
Reporter: Howard M. Lewis Ship
Priority: Minor
It would be cool if, in development mode, a special query parameter (for example) could trigger extra markup output that would identify which components rendered each portion of the markup. This would be great for tracking down rendering problems on complex pages where any of a number of components could be doing the rendering (especially useful when using Blocks extracted from foreign pages).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-751) Add a development mode option that
emits extra comments to identify which components are responsible for which
portions of the rendered markup
Posted by "Ulrich Stärk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721749#action_12721749 ]
Ulrich Stärk commented on TAP5-751:
-----------------------------------
Isn't that the same as in TAP5-742?
> Add a development mode option that emits extra comments to identify which components are responsible for which portions of the rendered markup
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-751
> URL: https://issues.apache.org/jira/browse/TAP5-751
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.2
> Reporter: Howard M. Lewis Ship
> Priority: Minor
>
> It would be cool if, in development mode, a special query parameter (for example) could trigger extra markup output that would identify which components rendered each portion of the markup. This would be great for tracking down rendering problems on complex pages where any of a number of components could be doing the rendering (especially useful when using Blocks extracted from foreign pages).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-751) Add a development mode option that
emits extra comments to identify which components are responsible for which
portions of the rendered markup
Posted by "Ulrich Stärk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721749#action_12721749 ]
Ulrich Stärk commented on TAP5-751:
-----------------------------------
Isn't that the same as in TAP5-742?
> Add a development mode option that emits extra comments to identify which components are responsible for which portions of the rendered markup
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-751
> URL: https://issues.apache.org/jira/browse/TAP5-751
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.2
> Reporter: Howard M. Lewis Ship
> Priority: Minor
>
> It would be cool if, in development mode, a special query parameter (for example) could trigger extra markup output that would identify which components rendered each portion of the markup. This would be great for tracking down rendering problems on complex pages where any of a number of components could be doing the rendering (especially useful when using Blocks extracted from foreign pages).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-751) Add a development mode option that emits
extra comments to identify which components are responsible for which
portions of the rendered markup
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-751:
--------------------------------------
Summary: Add a development mode option that emits extra comments to identify which components are responsible for which portions of the rendered markup (was: Add a development mode option that emits extra comments to identify which comments are responsible for which portions of the rendered markup)
> Add a development mode option that emits extra comments to identify which components are responsible for which portions of the rendered markup
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-751
> URL: https://issues.apache.org/jira/browse/TAP5-751
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.2
> Reporter: Howard M. Lewis Ship
> Priority: Minor
>
> It would be cool if, in development mode, a special query parameter (for example) could trigger extra markup output that would identify which components rendered each portion of the markup. This would be great for tracking down rendering problems on complex pages where any of a number of components could be doing the rendering (especially useful when using Blocks extracted from foreign pages).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-751) Add a development mode option that emits
extra comments to identify which components are responsible for which
portions of the rendered markup
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-751:
--------------------------------------
Summary: Add a development mode option that emits extra comments to identify which components are responsible for which portions of the rendered markup (was: Add a development mode option that emits extra comments to identify which comments are responsible for which portions of the rendered markup)
> Add a development mode option that emits extra comments to identify which components are responsible for which portions of the rendered markup
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-751
> URL: https://issues.apache.org/jira/browse/TAP5-751
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.2
> Reporter: Howard M. Lewis Ship
> Priority: Minor
>
> It would be cool if, in development mode, a special query parameter (for example) could trigger extra markup output that would identify which components rendered each portion of the markup. This would be great for tracking down rendering problems on complex pages where any of a number of components could be doing the rendering (especially useful when using Blocks extracted from foreign pages).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.