Fix badge tooltips not appearing in Manage Jenkins and Plugin Manager

[yoursanonymous]

Fixes #23866

The badge counting tooltips stopped appearing while hovering in the Manage Jenkins UI and in the Manage Plugin page that is also visible in the side panel when enabling the the Manage Jenkins UI.
This happens because the badge <span> elements no longer receive events.
As a result, Tippy.js initializes correctly on the <span> and $el._tippy.show() works, but hover never triggers the tooltip.

Testing done

Tested manually on a Jenkins WAR with this change:

• On Manage Jenkins: hovering the “Plugins” tile shows the tooltip.
• On Manage Plugins: hovering the “Updates” sidebar entry shows the tooltip.

Screenshots taken after confirm expected behavior.

Proposed changelog entries

Fix badge tooltips not appearing in the Plugin Manager and the Manage Jenkins UI by correctly computing tooltip padding and attaching the tooltip instance to the appropriate reference element.

Proposed changelog category

/label bug, web-ui

Proposed upgrade guidelines

N/A

Submitter checklist

• The issue, if it exists, is well-described.
• 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.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• UI changes do not introduce regressions when enforcing the current default rules of Content Security Policy Plugin. In particular, 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).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@jenkinsci/core-pr-reviewers
@timja

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

Maintainer checklist

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• 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).
• If it would make sense to backport the change to LTS, be a Bug or Improvement, and either the issue or pull request must be labeled as lts-candidate to be considered.

[mawinter69]

From the screenshots it looks as if the tooltips are a bit misplaced.

[yoursanonymous]

From the screenshots it looks as if the tooltips are a bit misplaced.

Thanks for checking the misalignment!
The slight offset in the screenshot is just the default Tippy/Popper placement based on available space. The main issue that the tooltip was not appearing at all is fixed in this Pull Request.
If needed, I can follow up with a separate PR to fine tune the visual positioning.

[mawinter69]

The root cause of the problem is #11254 which set pointer-events:none to the badges. When I remove this the tooltip is properly shown.
Removing that might have other side effects though.
@janfaracik

[yoursanonymous]

Thanks for pointing out the root cause.
This fix intentionally avoids removing the rule globally to prevent side effects. Instead, it attaches the tooltip to the nearest clickable ancestor, which preserve it's existing behavior.

[mawinter69]

Your solution is more of a hack. And potentially causes issues in situation where the tooltip should not be shown.
I think it is better to remove the pointer-events: none and check what side effects this has. And then only apply it to those cases where the pointer events should be avoided.
Best to wait for @janfaracik to look into this as the author of the change that introduced the problem.

[krisstern]

I am closing this as this does not seem to address the issue properly, is too hacky and may introduce problems later