You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2007/06/28 10:58:28 UTC

[jira] Commented: (STR-3055) Figure out the 'disabled="${!empty pageScope}" in EL-Example

    [ https://issues.apache.org/struts/browse/STR-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41299 ] 

Henri Yandell commented on STR-3055:
------------------------------------

So, dumb question. How do you control the pageScope emptiness through the app?

I don't recall ever seeing the boolean result change; so things were always disabled.

> Figure out the 'disabled="${!empty pageScope}" in EL-Example
> ------------------------------------------------------------
>
>                 Key: STR-3055
>                 URL: https://issues.apache.org/struts/browse/STR-3055
>             Project: Struts 1
>          Issue Type: Task
>          Components: Apps
>    Affects Versions: 1.3.9
>            Reporter: Henri Yandell
>            Assignee: Henri Yandell
>            Priority: Minor
>             Fix For: 1.3.10, 1.4.0
>
>
> The EL-Example has lots of 'disabled="${!empty pageScope}". This seems hugely confusing - why say that and not just 'true' or 'false'.
> At the minimum, need to explain when it's happening so people know a field is meant to be disabled.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.