fix(styling _table.scss): button tooltip style

[caocuong2404]

• fix button's background when hover was deviation

See JENKINS-74776.

Testing done

Proposed changelog entries

• Adjust the button's background styling when hovering a button with a tooltip.

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

@qerub @pengwynn @lucaspanjer @richievos @cris @jenkinsci/core-pr-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).

[welcome]

Yay, your first pull request towards Jenkins core was created successfully! Thank you so much!

A contributor will provide feedback soon. Meanwhile, you can join the chats and community forums to connect with other Jenkins users, developers, and maintainers.

[mawinter69]

I can't reproduce the problem locally on the current head without your fix.
Also in your screenshots it looks as if in the header there is a column missing as all headers are shifted by one column to the left.
Can you post a screenshot that shows the complete table.
Maybe the issue is caused by some other plugin

[caocuong2404]

I can't reproduce the problem locally on the current head without your fix. Also in your screenshots it looks as if in the header there is a column missing as all headers are shifted by one column to the left. Can you post a screenshot that shows the complete table. Maybe the issue is caused by some other plugin

Hi @mawinter69 , I apologize for not including the detailed information. It occurred on:
Microsoft Edge
Version 130.0.2849.56 (Official build) (arm64)

[mawinter69]

@caocuong2404 Did you read what I wrote?
Your screenshot looks suspicious as the header of the table is not correct.
So please provide a screenshot of the complete table and not just of the right part. Something else is wrong on your instance.
The fix you propose might still be valid though.

[MarkEWaite]

I can't duplicate the issue on my Microsoft Edge 130.0.2849.56 on amd64.

[MarkEWaite]

I have labeled this pull request as "stalled" due to no response in 3 weeks. If it remains without a response for another week, I'll close the pull request.