You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Geoff Callender (JIRA)" <ji...@apache.org> on 2013/12/12 01:56:07 UTC

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

Geoff Callender created TAP5-2259:
-------------------------------------

             Summary: 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: Bug
          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)