angular / angular/components

bug(Tooltip): Harness returns if _any_ tooltip is open

Ouverte
#26,773 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
area: material/tooltip P3
Langage dominant
TypeScript
Étoiles
25k
Forks
6.8k
Merge moyen
1 j 8 h
PR mergées (30 j)
91

Description

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

`MatTooltipHarness.isOpen()` returns `true` if _any_ tooltip is open. Intuitively it should returns if the tooltip _associated with that harness_ is open. The docs also sound like that's what it should do, because it uses the word "the" instead of "a":

> Gets whether the tooltip is open.

### Reproduction

Steps to reproduce:
1. Have tooltips on 2 elements
2. Open one of them
3. Test `.isOpen()` on the harness for a different one

Here's a stackblitz: https://stackblitz.com/edit/harness-issue-84mcjr?file=src/app/button-harness-example.spec.ts

### Expected Behavior

`.isOpen()` would return true for the tooltip that is open, and false for the one that is not

### Actual Behavior

`.isOpen()` returns true for both

### Environment

```
@angular-devkit/architect 0.1501.2
@angular-devkit/build-angular 15.1.2
@angular-devkit/core 15.0.5
@angular-devkit/schematics 15.0.5
@angular/cdk 15.0.3
@angular/cli 15.0.5
@angular/fire 7.5.0
@angular/material 15.0.3
@schematics/angular 15.0.5
rxjs 7.5.7
typescript 4.8.4
```

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Start by locating MatTooltipHarness.isOpen() and the associated tooltip harness tests. Reproduce the two-tooltip case from the issue, then verify that isOpen() distinguishes the tooltip associated with the harness from other open tooltips; the relevant test should pass for both the open and closed harnesses.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
angular, typescript
Domaine
frontend, testing
Type d'issue
Bug
Difficulté
3/5
Temps estimé
1-2 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
52/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.