You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Julien Martin (Created) (JIRA)" <ji...@apache.org> on 2012/01/24 11:42:40 UTC
[jira] [Created] (TAP5-1827) It shoud be possible to customize
kaptcha field so that it allows input type = text instead of input type=
password
It shoud be possible to customize kaptcha field so that it allows input type = text instead of input type= password
-------------------------------------------------------------------------------------------------------------------
Key: TAP5-1827
URL: https://issues.apache.org/jira/browse/TAP5-1827
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-kaptcha
Affects Versions: 5.3.1
Reporter: Julien Martin
Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1827) It shoud be possible to customize
kaptcha field so that it allows input type = text instead of input type=
password
Posted by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1827.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.4
5.3.3
> It shoud be possible to customize kaptcha field so that it allows input type = text instead of input type= password
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1827) KaptchaField should have a parameter
to allow it to operate as a visible text field rather than a password field
Posted by "Howard M. Lewis Ship (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1827:
---------------------------------------
Summary: KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field (was: It shoud be possible to customize kaptcha field so that it allows input type = text instead of input type= password)
> KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1827) KaptchaField should have a parameter
to allow it to operate as a visible text field rather than a password field
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233878#comment-13233878 ]
Hudson commented on TAP5-1827:
------------------------------
Integrated in tapestry-5.3-freestyle #15 (See [https://builds.apache.org/job/tapestry-5.3-freestyle/15/])
TAP5-1827: It shoud be possible to customize kaptcha field so that it allows input type=text instead of input type=password (Revision 1303130)
Result = FAILURE
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1303130
Files :
* /tapestry/tapestry5/branches/5.3/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/KaptchaSymbolConstants.java
* /tapestry/tapestry5/branches/5.3/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/components/KaptchaField.java
* /tapestry/tapestry5/branches/5.3/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/components/KaptchaImage.java
* /tapestry/tapestry5/branches/5.3/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/services/KaptchaModule.java
> KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1827) It shoud be possible to customize
kaptcha field so that it allows input type = text instead of input type=
password
Posted by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1827.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.4
5.3.3
> It shoud be possible to customize kaptcha field so that it allows input type = text instead of input type= password
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1827) KaptchaField should have a parameter
to allow it to operate as a visible text field rather than a password field
Posted by "Howard M. Lewis Ship (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1827:
---------------------------------------
Summary: KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field (was: It shoud be possible to customize kaptcha field so that it allows input type = text instead of input type= password)
> KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1827) KaptchaField should have a parameter
to allow it to operate as a visible text field rather than a password field
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233751#comment-13233751 ]
Hudson commented on TAP5-1827:
------------------------------
Integrated in tapestry-trunk-freestyle #691 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/691/])
TAP5-1827: It shoud be possible to customize kaptcha field so that it allows input type=text instead of input type=password (Revision 1303131)
Result = SUCCESS
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1303131
Files :
* /tapestry/tapestry5/trunk/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/KaptchaSymbolConstants.java
* /tapestry/tapestry5/trunk/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/components/KaptchaField.java
* /tapestry/tapestry5/trunk/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/components/KaptchaImage.java
* /tapestry/tapestry5/trunk/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/services/KaptchaModule.java
> KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1827) KaptchaField should have a parameter
to allow it to operate as a visible text field rather than a password field
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233878#comment-13233878 ]
Hudson commented on TAP5-1827:
------------------------------
Integrated in tapestry-5.3-freestyle #15 (See [https://builds.apache.org/job/tapestry-5.3-freestyle/15/])
TAP5-1827: It shoud be possible to customize kaptcha field so that it allows input type=text instead of input type=password (Revision 1303130)
Result = FAILURE
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1303130
Files :
* /tapestry/tapestry5/branches/5.3/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/KaptchaSymbolConstants.java
* /tapestry/tapestry5/branches/5.3/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/components/KaptchaField.java
* /tapestry/tapestry5/branches/5.3/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/components/KaptchaImage.java
* /tapestry/tapestry5/branches/5.3/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/services/KaptchaModule.java
> KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1827) KaptchaField should have a parameter
to allow it to operate as a visible text field rather than a password field
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233751#comment-13233751 ]
Hudson commented on TAP5-1827:
------------------------------
Integrated in tapestry-trunk-freestyle #691 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/691/])
TAP5-1827: It shoud be possible to customize kaptcha field so that it allows input type=text instead of input type=password (Revision 1303131)
Result = SUCCESS
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1303131
Files :
* /tapestry/tapestry5/trunk/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/KaptchaSymbolConstants.java
* /tapestry/tapestry5/trunk/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/components/KaptchaField.java
* /tapestry/tapestry5/trunk/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/components/KaptchaImage.java
* /tapestry/tapestry5/trunk/tapestry-kaptcha/src/main/java/org/apache/tapestry5/kaptcha/services/KaptchaModule.java
> KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1827) It shoud be possible to customize
kaptcha field so that it allows input type = text instead of input type=
password
Posted by "Howard M. Lewis Ship (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1827:
------------------------------------------
Assignee: Howard M. Lewis Ship
> It shoud be possible to customize kaptcha field so that it allows input type = text instead of input type= password
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (TAP5-1827) It shoud be possible to customize
kaptcha field so that it allows input type = text instead of input type=
password
Posted by "Howard M. Lewis Ship (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reopened TAP5-1827:
----------------------------------------
> It shoud be possible to customize kaptcha field so that it allows input type = text instead of input type= password
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1827) It shoud be possible to customize
kaptcha field so that it allows input type = text instead of input type=
password
Posted by "Howard M. Lewis Ship (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1827:
------------------------------------------
Assignee: Howard M. Lewis Ship
> It shoud be possible to customize kaptcha field so that it allows input type = text instead of input type= password
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1827) KaptchaField should have a parameter to
allow it to operate as a visible text field rather than a password field
Posted by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1827.
--------------------------------------
Resolution: Fixed
> KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (TAP5-1827) It shoud be possible to customize
kaptcha field so that it allows input type = text instead of input type=
password
Posted by "Howard M. Lewis Ship (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reopened TAP5-1827:
----------------------------------------
> It shoud be possible to customize kaptcha field so that it allows input type = text instead of input type= password
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1827) KaptchaField should have a parameter to
allow it to operate as a visible text field rather than a password field
Posted by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1827.
--------------------------------------
Resolution: Fixed
> KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1827
> URL: https://issues.apache.org/jira/browse/TAP5-1827
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-kaptcha
> Affects Versions: 5.3.1
> Reporter: Julien Martin
> Assignee: Howard M. Lewis Ship
> Labels: input, kaptcha, password, text, type
> Fix For: 5.3.3, 5.4
>
>
> Most captcha implementations are based on input type=text instead of input type=password. It would be nice to allow for both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira