<f:entry title="${%title.aggregatingResults}" field="aggregatingResults">
<f:checkbox/>
</f:entry>
Before the change I had a short label as title
and a sentence as a description
of the checkbox. E.g., title
= Skip Symbolic Links and description
= Toggle whether the file scanner will skip symbolic links. (The label came before the checkbox and the description is below the field). This does not look good with the new UI where the checkbox comes before the label. So I changed that: I removed the description and used a longer label for the title
, e.g. Skip symbolic links when searching for files.
When I look at the Build Trigger checkboxes, they look good in old and new UI. Seems they use a different approach...
We had a mini UX SIG Meeting that lasted the whole of 3 minutes in which we briefly touched on Tables to Div migration progress. Hopefully next session a few more people will be back from holiday.
The recording is available here: https://youtu.be/Pn7Om1veVyI
The minutes are available here: https://docs.google.com/document/d/1xA6UN7ORv3OFYBC3Kw6y4mtqDekAjwYVNhsrH4PBwBk/edit#heading=h.tzojjx53eatx
hetero-list
and repeatable
to fix https://issues.jenkins.io/browse/JENKINS-64291. I'd appreciate any sort of testing on this one, as it's a bit tricky.