[jira] [Commented] (CAUSEWAY-3960) [Wicket Viewer] Actions in Tables have wrong Usability/Visibility Logic

2026-01-20 Thread Andi Huber (Jira)


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

Andi Huber commented on CAUSEWAY-3960:
--

I had made some related refactoring attempts, but never merged because the 
number of Java files that needed changes exploded:
https://github.com/apache/causeway/pull/3285

I remember that I found little inconsistencies there as well.

Fixing this will require a revisiting of above mentioned PR as well.



> [Wicket Viewer] Actions in Tables have wrong Usability/Visibility Logic
> ---
>
> Key: CAUSEWAY-3960
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3960
> Project: Causeway
>  Issue Type: Bug
>  Components: Viewer Wicket
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
>  Labels: end-user-visible
> Fix For: 3.6.0, 4.0.0
>
>
> If an Action is disabled for Forms but enabled for Tables, then it should be 
> visible in Tables but is not. Same for Usability.
> In ActionLinksPanel we only ever check for form-visibility/-usability, but 
> instead it should be sensitive to the context we are rendering it in (either 
> form or table). 



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


[jira] [Commented] (CAUSEWAY-3960) [Wicket Viewer] Actions in Tables have wrong Usability/Visibility Logic

2026-01-20 Thread Andi Huber (Jira)


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

Andi Huber commented on CAUSEWAY-3960:
--

Can be reproduced with the demo app. Go to Actions -> Hidden, it should render 
a table that has a populated action column. (But it has not.)

> [Wicket Viewer] Actions in Tables have wrong Usability/Visibility Logic
> ---
>
> Key: CAUSEWAY-3960
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3960
> Project: Causeway
>  Issue Type: Bug
>  Components: Viewer Wicket
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 3.6.0, 4.0.0
>
>
> If an Action is disabled for Forms but enabled for Tables, then it should be 
> visible in Tables but is not. Same for Usability.
> In ActionLinksPanel we only ever check for form-visibility/-usability, but 
> instead it should be sensitive to the context we are rendering it in (either 
> form or table). 



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