You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2008/09/15 22:13:44 UTC
[jira] Resolved: (WICKET-1830) Include Component Path in Generated
Markup
[ https://issues.apache.org/jira/browse/WICKET-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-1830.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4-M4
1.3.5
i waited a couple of days james, but didnt see a patch so i put this in myself as it is also useful to us for our selenium tests
> Include Component Path in Generated Markup
> ------------------------------------------
>
> Key: WICKET-1830
> URL: https://issues.apache.org/jira/browse/WICKET-1830
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: James Carman
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.3.5, 1.4-M4
>
>
> For unit testing purposes, it would be nice to know the exact ids of the components on your wicket pages. Perhaps the generated markup could contain a wicket:path attribute?
> <div wicket:path="some:path:to:this:div">
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.