tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Massimo Lusetti (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-742) Add optional component tracing comments to rendered output
Date Wed, 10 Jun 2009 13:46:07 GMT

    [ https://issues.apache.org/jira/browse/TAP5-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718084#action_12718084
] 

Massimo Lusetti commented on TAP5-742:
--------------------------------------

Yep, just a query parameter seems too much easy as Ulrich proposed a production-mode could
be leveraged for this purpose.

> Add optional component tracing comments to rendered output
> ----------------------------------------------------------
>
>                 Key: TAP5-742
>                 URL: https://issues.apache.org/jira/browse/TAP5-742
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>
> In complex pages, it can be hard to work backwards from a bit of output HTML in the browser,
back to the component that originated the markup.
> A special mode could be enabled where components would render a comment before and after
rendering:
> <!-- BEGIN: Index:layout.pagelink -->
> <a href="dashboard">Dashboard</a>
> <!-- END: Index:layout.pagelink -->
> This would bloat and clutter the application (a lot!) but would be useful, on occasion.
 One possibility would be a special query parameter to enable this on a request-by-request
basis, i.e., ?t:component-trace=true

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message