fix(AgenticRetry): hide retry tooltip while loading without root events

What does this MR do?

Hides the Retry tooltip of AgenticRetry while loading without bootstrap-vue's root event bus.

The upcoming major version of @gitlab/ui (gitlab-org/gitlab-services/design.gitlab.com!6294 (merged)) replaces bootstrap-vue's tooltip with a Popover API based one, and drops the bv::show::tooltip / bv::hide::tooltip root events. AgenticRetry emitted bv::hide::tooltip to hide the Retry tooltip when loading starts. It's the only such call in Duo UI. With the new @gitlab/ui, nothing listens to it anymore, so the tooltip would stay open while loading.

Duo UI's peer range for @gitlab/ui is >=112.3.1, so the fix has to work with both the current and the new major:

  • The new showGlTooltip / hideGlTooltip exports only exist in the new major.
  • A disabled tooltip binding doesn't work in the current one: bootstrap-vue keeps an already open tooltip open when it becomes disabled.
  • An empty title works in both: both hide an open tooltip whose title becomes empty.

So the Retry button now empties its title while loading, and the watcher with the root event is gone. The button keeps its accessible name through its unchanged aria-label.

How it was verified

  • With the real directive, not the mock, on @gitlab/ui 139 (bootstrap-vue): an open Retry tooltip closes when loading starts.
  • With the real directive on the new @gitlab/ui from !6294, in Vue 2 and 3: an open tooltip closes when loading starts, the title is back afterwards, and hovering opens it again.
  • New spec cases: the title is empty while loading, aria-label is kept, and the title is restored after loading. The spec passes in Vue 2 and 3. ESLint, Prettier and yarn type-check pass.

How to test

  1. Open an agentic chat with a Retry button and hover it, so its tooltip opens.
  2. Click Retry: the tooltip closes while loading.
  3. After loading, hover it again: the tooltip opens with "Retry".

Screenshots or screen recordings

None: no visual change.

Integration merge requests

None needed: the change works with the @gitlab/ui version gitlab-org/gitlab uses today. It prepares Duo UI for the new major in gitlab-org/gitlab-services/design.gitlab.com!6294 (merged). This MR should be released, and picked up by gitlab-org/gitlab, before that major.

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidelines.
  • If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
  • Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/product-security/psirt-group
  • Security reports checked/validated by a reviewer from the PSIRT team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.

Merge request reports

Loading
Loading