[jira] [Commented] (TAP5-2223) New "secure" flag in Select component has a bug when using option groups

["François Facon (JIRA)" <ji...@apache.org>]

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

François Facon commented on TAP5-2223:
--------------------------------------

Thank you julien.
Your example will help me to provide a test case. 

Regards
François

> New "secure" flag in Select component has a bug when using option groups
> ------------------------------------------------------------------------
>
>                 Key: TAP5-2223
>                 URL: https://issues.apache.org/jira/browse/TAP5-2223
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Felix Gonschorek
>            Assignee: François Facon
>            Priority: Minor
>         Attachments: OptionGroup.zip
>
>
> Version 5.4 alpha 25
> Component: Select
> Method: org.apache.tapestry5.corelib.components.Select.findValueInModel
> When checking for exististence of selected value on submit, there is a bug when checking in option groups: the string representation is used to compare with objects ("asSubmitted" should be used but "submittedValue" is used)
> This bug was introduced with: TAP5-2179
> workaround: disable security check for select component.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)