[jira] [Commented] (TAP5-2259) Select should allow secure="never", but requires secure="literal:never"

["Bob Harner (JIRA)" <ji...@apache.org>]

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

Bob Harner commented on TAP5-2259:
----------------------------------

I agree with you, Geoff. I'm willing to make this small change in the next couple days unless somebody presents a compelling case for leaving it as is.

> Select should allow secure="never", but requires secure="literal:never"
> -----------------------------------------------------------------------
>
>                 Key: TAP5-2259
>                 URL: https://issues.apache.org/jira/browse/TAP5-2259
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Geoff Callender
>            Priority: Minor
>
> Select's secure parameter is new to 5.4 and it would be nice to change this before the first release.
> Select should allow secure="never" instead of secure="literal:never". Currently the default is PROP, but I'm hard-pressed to think of a case where you'd want to set it with a property.
> Some useful precedents: 
> - Select allows blankoption="always".
> - TextField allows nulls="zero".
> - Any AbstractField allows disabled="true".



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)