Most of the work we did to improve the visualization of nested content was actually done with this very interaction in mind. There's always the chance to improve it so we are really open to suggestions.

Once https://github.com/jenkinsci/jenkins/pull/4820 is released, the issue will appear in UIs for Jenkins users

To be clear, as far as I know the core change does not make anything worse for this screen. Rather, the point of this issue is that it may enable us to go back to more straightforward and intuitive control structure without putting up with ridiculously deep indentation, the motivation for the hack done in JENKINS-38712.

jglick now that the form changes have been released in 2.264, do you know if this affects any screens? If so, what repos may be affected? I can do a code search in those repos and report the individual findings.

fqueiruga not sure I understand the question. This is just about simplifying the GUI config screen for Groovy libraries to use an intuitive block structure like it did originally, rather than nested radio buttons like we were forced to use in order to avoid deep indentation when using tables.

Ah, I see. So we shouldn't include it in the tables-to-divs regression epic right?

Right, it's not a regression, it's an opportunity to partially revert a hack.