-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modernise the 'New view' and 'New node' pages #5842
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a GREAT PR. Congratulations!!!!! 🎉 I do have a few comments if you don't mind:
- 350px inputs are way too short for. Going for ~700px/43rem is always a solid choice.
- I think you could very well go all in with the configuration. Stuff like padding, label font weight, box shadows, etc.
- Border radius should IMO be 4px to be consistent with the rest of the UI and plugins.
My only -1 would be having custom buttons. I don't think there's any need for that. Existing buttons are widely used and won't probably be changed. And if they need changes, it should be global IMO. This is coming from my personal experience with the buttons revamp last year.
Also, have you tried applying these styles to the .setting-input
class, just to see what happens? Any long term form strategy to update inputs would be most effective by acting on that class.
war/src/main/less/modules/form.less
Outdated
background: var(--input-color); | ||
border: 2px solid var(--input-border); | ||
padding: 8px; | ||
border-radius: 6px; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
4px would be more consistent with the rest of the UI and with the plugins using bootstrap.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think once the rest of the components are merged in (working on a branch with all the rest now) things will look a lot more consistent and behave far better so for that reason I'd rather we stick with the slightly rounder 6px. I have made it into a CSS variable though so it would be easy to change :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, appreciate the expansion of the configuration.
JENKINS-67071 suggests this causes a regression in job config forms. |
Addressed in #5893 |
After pulling in this commit, I can no longer add a Maven installation via the UI (see JENKINS-67109). |
@janfaracik This PR breaks the following tests and blocks weekly updates to the BOM (cf. jenkinsci/bom#717 and jenkinsci/bom#719):
The tests will need to be adapted to this PR and new versions of the abovementioned plugins released. |
I have changed locally that fixes most of those, there’s one test i’m still debugging |
Also breaks |
I'm not sure if someone is still is working on the problematic width resolution change within this PR, I created an issue so this will not be forgotten: https://issues.jenkins.io/browse/JENKINS-67198 |
The screenshots above even show the fixed minimal width |
It's being addressed to a degree in #5923 There's additional work coming as well that was demoed in the previous UX sig meeting, around here: Plenty of open PRs in this area: Generally getting held up either adjusting tests to markup or fixing issues, but hopefully we'll get most of them merged in December |
Thanks @timja, appreciate it! Great work! |
Is anyone looking at this question, it really bothers me |
I am :) It'll be updated as part of #5923, I've posted a WIP screenshot on the Jira thread if you're interested. |
Causes JENKINS-68042 |
<a href="#" class="help-button" helpURL="${rootURL}${attrs.url}"><l:helpIcon class="icon-help" tooltip="${altText}"/></a> | ||
</span> | ||
<j:set var="altText" value="${attrs.featureName != null ? '%Help for feature:' + ' ' + attrs.featureName : '%Help'}" /> | ||
<a href="#" class="jenkins-help-button" tooltip="${altText}" helpURL="${rootURL}${attrs.url}"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Caused SECURITY-2779
Caused JENKINS-69030 |
Contributed to JENKINS-69549. |
.jenkins-search { | ||
position: relative; | ||
max-width: 420px; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Caused JENKINS-71115.
Caused JENKINS-72749 |
What's changed?
This PR updates the appearance of several (not all!) form controls to give Jenkins a more modern, consistent appearance. The main focus of this PR is to modernise the 'New view' and 'New node' pages, however, some of the changes, such as the change in
input
design will ripple throughout Jenkins.The end goal would be to update all the form controls across Jenkins, ensuring consistency, modernity and better accessibility throughout the service.
Test this pull request
Screenshots
Old
New
Old
New
New.node.2.mov
Proposed changelog entries
Submitter checklist
Proposed changelog entries
section only if there are breaking changes or other changes which may require extra steps from users during the upgradeDesired reviewers
@mention
Maintainer checklist
Before the changes are marked as
ready-for-merge
:Proposed changelog entries
are correctupgrade-guide-needed
label is set and there is aProposed upgrade guidelines
section in the PR title. (example)lts-candidate
to be considered (see query).