[JENKINS-75892] Set the default enter delay for tooltips to 500 msec

[uhafner]

Tooltips should not pop up immediately, rather they should use a small delay. Otherwise, tooltips show up while the user still is moving the mouse. I set the delay to 500 msec, which seems to be a reasonable setting for Jenkins' views.

See JENKINS-75892.

Testing done

Manually tested in my local Jenkins instance. I see no way to provide a test for this change.

Proposed changelog entries

• Set the default enter delay for tooltips to 500 msec

Proposed changelog category

/label bug

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira 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.
• 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

@timja @janfaracik @jenkinsci/sig-ux

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, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[comment-ops-bot]

I wasn't able to add the following labels: bug web-ui

Check that the label exists and is spelt right then try again.

[janfaracik]

Thanks - I'll take a look.

[janfaracik]

I don''t mind the delay but I think it could be sped up a little, also it'd be cool if subsequent hovers were instant, i.e. they don't have the same delay.