Description of problem: When a developer accesses Deployment panel in Admin perspective for a project with view-only access, the Actions menu is still available for clicking but nothing happens. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Setup an application in a project with a deployment. 2. Assign view-only access to the project to some username. 3. Log in as that username, navigate to "Deployment" panel in Admin perspective. 4. Click on "Actions" pull-down menu and click on any Action. Actual results: Action is clickable and gets highlighted, but nothing happens. Expected results: Actions menu is not available for deployments in view-only projects. Additional info:
(In reply to Parag from comment #0) > Description of problem: > > When a developer accesses Deployment panel in Admin perspective for a > project with view-only access, the Actions menu is still available for > clicking but nothing happens. > > Version-Release number of selected component (if applicable): > > > How reproducible: > > Always > > Steps to Reproduce: > 1. Setup an application in a project with a deployment. > 2. Assign view-only access to the project to some username. > 3. Log in as that username, navigate to "Deployment" panel in Admin > perspective. > 4. Click on "Actions" pull-down menu and click on any Action. > > Actual results: > > Action is clickable and gets highlighted, but nothing happens. > > Expected results: > > Actions menu is not available for deployments in view-only projects. > > Additional info: Hi @pdave, have followed the steps as mentioned, and currently action menus are disabled based on the design for the user with view-only access and thus it's shown but not clickable. Have attached a screenshot for both with view access and edit access.
Created attachment 1781740 [details] user with view access
Created attachment 1781741 [details] user with edit access
Thanks, Jai! Yes, the actions are disabled but I can click on them (a blue border shows up around the clicked item, and in some cases, it takes a while for the UI to be responsive again.) Ideally, the whole menu should not be visible, even though it is disabled. Or maybe gray-out the Actions that are not allowed. Thanks!
A disabled action should not be clickable and also not focusable. We should leave the discussion as to whether or not the disable action is present to another bug fix as there are some discussions going on related to this. It's a bit trickier because we want to avoid flickering and delays in the UI while some actions require async permissions and other checks to determine if they should be enabled or not.
verified on 4.8.0-0.nightly-2021-06-02-025513
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438