[ 
https://issues.apache.org/jira/browse/CAUSEWAY-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Keir Haywood updated CAUSEWAY-3455:
------------------------------------------
    Description: 
in the demo app, use 

prog model >Composite Value Types

The page object shows a single value (a complex number type) which starts off 
being set to 1+0i.  The idea of the "addComplexNumber" action is to allow the 
end-user to add a value to this, eg "2 +3i" to result in "3 + 3i".  To make it 
more obvious that they are adding to the value held by the page object, the 
first parameter of this action is defaulted to the value from the page object, 
and is set to be disabled.

The defaulting works fine, and the UI looks fine:

!image-2023-05-09-07-01-53-626.png|width=212,height=119!

, however... it IS actually possible to click into the disabled field and set a 
value:

!image-2023-05-09-07-02-46-248.png|width=247,height=261!

 

  was:
in the demo app, use 
Domain Objects >Composite Value Types

The page object shows a single value (a complex number type) which starts off 
being set to 1+0i.  The idea of the "addComplexNumber" action is to allow the 
end-user to add a value to this, eg "2 +3i" to result in "3 + 3i".  To make it 
more obvious that they are adding to the value held by the page object, the 
first parameter of this action is defaulted to the value from the page object, 
and is set to be disabled.

The defaulting works fine, and the UI looks fine:

!image-2023-05-09-07-01-53-626.png|width=212,height=119!

, however... it IS actually possible to click into the disabled field and set a 
value:

!image-2023-05-09-07-02-46-248.png|width=247,height=261!

 


> [demo app] disable action param doesn't disable if a composite value type.
> --------------------------------------------------------------------------
>
>                 Key: CAUSEWAY-3455
>                 URL: https://issues.apache.org/jira/browse/CAUSEWAY-3455
>             Project: Causeway
>          Issue Type: Bug
>          Components: Demo App, Viewer Wicket
>    Affects Versions: 2.0.0-RC1
>            Reporter: Daniel Keir Haywood
>            Priority: Minor
>             Fix For: 2.0.0-RC2
>
>         Attachments: image-2023-05-09-07-01-53-626.png, 
> image-2023-05-09-07-02-46-248.png
>
>
> in the demo app, use 
> prog model >Composite Value Types
> The page object shows a single value (a complex number type) which starts off 
> being set to 1+0i.  The idea of the "addComplexNumber" action is to allow the 
> end-user to add a value to this, eg "2 +3i" to result in "3 + 3i".  To make 
> it more obvious that they are adding to the value held by the page object, 
> the first parameter of this action is defaulted to the value from the page 
> object, and is set to be disabled.
> The defaulting works fine, and the UI looks fine:
> !image-2023-05-09-07-01-53-626.png|width=212,height=119!
> , however... it IS actually possible to click into the disabled field and set 
> a value:
> !image-2023-05-09-07-02-46-248.png|width=247,height=261!
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to