[border_css_util] implement css helper class

[scherler]

This PR will provide CSS helper classes to add borders. It is similar to https://weekly.ci.jenkins.io/design-library/Spacing/ but takes more the way https://tailwindcss.com/docs/border-width works e.g. jenkins-border-t-3 will create a top border of 3 px

follow up pr will be created for https://weekly.ci.jenkins.io/design-library

Testing done

After compile you can change the source code to

    <div class="jenkins-border-t-4">
      Hello border
    </div>
    <div class="jenkins-border-dashed jenkins-border-b jenkins-border-t jenkins-border-blue">
      Hello border
    </div>
    <div class="jenkins-border jenkins-border-green">
      Hello border
    </div>

Proposed changelog entries

CSS helper classes to add borders in the spirit of the jenkins-!-spacing

Proposed upgrade guidelines

N/A

Submitter checklist

Preview Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

Preview Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[janfaracik]

Hey, thanks!

Is there a specific use case for these utils? Curious, wondering if it should be like the colours where we have a base palette but then a semantic set on top of them with specific meaning.

[scherler]

Mainly I was looking into this because of yui-button has borders but jenkins-button does not, some of our designs need those borders. Regarding the semantics I can implement that

[janfaracik]

Mainly I was looking into this because of yui-button has borders but jenkins-button does not, some of our designs need those borders. Regarding the semantics I can implement that

Ah gotcha. Is there any chance you could share a pic of what those buttons look like? Might be worth making a new type of button rather than a util library if its limited to that.

[scherler]

this image shows a typical use case.

[scherler]

... to be honest (but that is me loving CSS util classes) I think the border helper is much more versatile and it is in the spirit of the spacing util classes

[scherler]

I have created a PoC

• Analyze now = .jenkins-button--primary-inverted
• Turn off = .jenkins-button--danger
• Download = .jenkins-button--success

.jenkins-button--primary-inverted {
  color: var(--btn-secondary-color) !important;
  border: 2px solid var(--btn-secondary-border);
  border-radius: 4px;
  font-weight: bold;
  font-size: var(--font-size-xs);
  &::before {
      background: transparent !important;
    }
    
    &:not(:disabled) {
        &:hover {
            border: 2px solid var(--accent-color) !important;
            color: var(--accent-color) !important;
    }

    &:active,
    &:focus-visible {
      &::before {
        opacity: 0.8;
      }

      &::after {
        box-shadow: 0 0 0 0.33rem var(--accent-color);
        opacity: 0.2;
      }
    }
  }
}

.jenkins-button--danger {
  color: var(--white) !important;
  background-color: var(--destructive-color);
  border-color: var(--destructive-color);
  font-weight: bold;
  font-size: var(--font-size-xs);
  
  &:not(:disabled) {
    &:hover,
    &:focus {
        color: var(--white);
        background-color: var(--danger-hover);
        border-color: var(--danger-hover);
    }
  }
  
  &:focus {
    box-shadow: 0 0 0 0.2rem var(--danger-active);
  }
  
  &:active {
    color: var(--white);
    background-color: var(--danger-active);
    border-color: var(--danger-active);
  }
}

.jenkins-button--success {
  color: var(--white) !important;
  background-color: var(--success-color);
  border-color: var(--success-color);
  font-weight: bold;
  font-size: var(--font-size-xs);
  
  &:not(:disabled) {
    &:hover,
    &:focus {
        color: var(--white);
        background-color: var(--light-green);
        border-color: var(--light-green);
    }
  }
  
  &:focus {
    box-shadow: 0 0 0 0.2rem var(--light-green);
  }
  
  &:active {
    color: var(--white);
    background-color: var(--light-green);
    border-color: var(--light-green);
  }
}

[scherler]

created an alternative PR #10061

[A1exKH]

created an alternative PR #10061

@scherler could you share information about this PR, please? As I understood it can be closed.