Experimental Manage Jenkins UI clips Matrix Authorization grid

[JoshHarmon]

Jenkins and plugins versions report

Environment

Jenkins 2.541.1
matrix-auth 3.2.9

What Operating System are you using (both controller, and any agents involved in the problem)?

N/A

Reproduction steps

1. Enable new-manage-jenkins.flag.
2. Navigate to Manage Jenkins > Security, and scroll to the Authorization section. Use Project-based Matrix Authorization Strategy or Matrix-based security.

Expected Results

Permission columns are not cut off, and user/group names are not unreasonably cramped/wrapped.

From the non-experimental UI:

Actual Results

Permission columns are cut off, Grant All/Remove All/Delete buttons are unavailable, and user/group names are (IMO) unreasonably cramped/wrapped.

Anything else?

#11222
I suppose in theory this could be blamed on the plugin (and other plugins that add permissions) for having/causing unusually wide UI, but given how widely installed this plugin is (91%), and its mention in the handbook, breaking it seems to me like an unacceptable regression in core behavior.

Are you interested in contributing a fix?

Sorry, I don't have the background or time to effectively do so.

[snappbandit]

Hi Maintainers, I am interested in contributing a fix for this, can be assigned to me?

[timja]

We do not assign issues. What is your proposed fix? Please don’t open a PR yet

[dhanush-raja-a]

hey dude i trying to reproduce the bug,
i want to know how to (Enable new-manage-jenkins.flag.)
currently i clone and trying to reproduce the isseue !!!

[dhanush-raja-a]

@JoshHarmon hi , I cloned the project and tried running it locally without enabling the new-manage-jenkins flag "i mean i did know what flag here means , bcs i am new ", but I still see some permission columns getting cut off in the Matrix / Project-based Matrix Authorization UI." by default"

Can you please confirm if this is expected?
If yes, I’ll proceed with investigating and trying to fix the layout issue. to make it fit with in the screen,

most the bug in any one of css,

[daniel-beck]

@dhanush-raja-a In the existing layout, you can at least scroll horizontally to access the additional checkboxes (or make the window larger, or zoom out). That's not possible in the experimental UI. So while it's not great, the problem is exacerbated in the experimental UI.

Please make an effort to communicate clearly. The run-on sentence and random looking punctuation in your post makes it difficult to understand.

[dhanush-raja-a]

@daniel-beck hi, sorry about the unclear wording in my earlier comment — I’m still getting used to communicating here, and I appreciate your patience.

Thank you for clarifying the difference between the existing UI and the experimental one. That makes sense now — the key issue is that horizontal scrolling is no longer possible in the experimental Manage Jenkins UI, which makes the clipping much worse.

Could you please help me understand how to enable the new-manage-jenkins.flag locally so I can switch to the experimental UI and reproduce the issue correctly?
I’ve cloned the Jenkins core repo and am running it locally, but I’m not sure where or how experimental flags are supposed to be activated.

Any guidance or pointers would be really helpful. Thanks again for your time and feedback.

[dhanush-raja-a]

@daniel-beck @JoshHarmon @timja
I was able to reproduce the issue locally and have implemented a CSS-only fix in the experimental Manage Jenkins UI.

What I changed
• Updated the layout styles in _build.scss
• Adjusted the grid/container behavior so the Matrix / Project-based Matrix Authorization table:
• no longer clips permission columns
• allows proper horizontal scrolling
• keeps the Grant All / Remove All / Delete buttons accessible

After the change, the UI behaves much closer to the non-experimental layout, but without breaking the new design structure.

Current status
• The fix works locally on my setup
• No Java or Jelly changes — CSS only(in css "i remove 3 line and added 20 line of code thats it no more change made")
• Scoped specifically to the problematic layout

Before opening a PR, I wanted to check:
• Does this approach align with the intended direction of the experimental UI?
• Are there any layout or accessibility considerations you’d like me to account for?
• Would you prefer a different styling strategy (e.g., wrapper-based scrolling vs table overflow)?

I’m happy to iterate or improve this further based on your feedback. Thanks for the guidance so far.

[dhanush-raja-a]

@JoshHarmon @timja I’ve opened PR #26186 with a CSS-only fix for the experimental Manage Jenkins UI.
It restores horizontal scrolling for the Matrix / Project-based Matrix
Authorization grid without affecting the classic UI.

[dhanush-raja-a]

I’ve opened PR #26191 to address this issue using a CSS-only fix scoped to the experimental UI.

[dhanush-raja-a]

\CI seems to be failing early in Linux/Windows JDK build jobs with a generic exit code.
This PR contains only UI/CSS changes, and ATH UI tests are passing.
Could you please advise if this looks like CI flakiness or if any action is needed from my side?

[daniel-beck]

[2026-01-27T14:57:05.621Z] Failed to run task: 'corepack yarn lint:ci' failed.
[2026-01-27T14:57:05.621Z] com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'corepack yarn lint:ci' failed.

https://github.com/jenkinsci/jenkins/blob/b13dd5dbfb5a4372a007b4599198848861417365/CONTRIBUTING.md#linting