ionic-team / ionic-team/ionic-framework

bug: setting an ion-label's textContent early results in double labels

Ouverte
#30,749 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
stencil type: bug
Langage dominant
TypeScript
Étoiles
52.7k
Forks
13.3k
Merge moyen
1 j 15 h
PR mergées (30 j)
51

Description

### Prerequisites

- [x] I have read the [Contributing Guidelines](https://github.com/ionic-team/ionic-framework/blob/main/docs/CONTRIBUTING.md#creating-an-issue).
- [x] I agree to follow the [Code of Conduct](https://ionicframework.com/code-of-conduct).
- [x] I have searched for [existing issues](https://github.com/ionic-team/ionic-framework/issues) that already report this problem, without success.

### Ionic Framework Version

v8.x

### Current Behavior

When setting a new `` instance's `textContent` before it is attached to the document and then after attaching it re-assigning a new `textContent` value will leave both visible.

See: https://codepen.io/ErikOnBike/pen/XJXqZxR

### Expected Behavior

The second assignment to the `textContent` property should remove the existing `textContent` value.

### Steps to Reproduce

See: https://codepen.io/ErikOnBike/pen/XJXqZxR

### Code Reproduction URL

https://codepen.io/ErikOnBike/pen/XJXqZxR

### Ionic Info

n/a

### Additional Information

This might be the effect of StencilJS' textContent patching. I'm not sure if I fully understand why StencilJS does all kinds of patching for WebComponents. It overrides things like `children`, `childNodes` and `textContent` which results in awkward behaviour if you're not following the standard Angular/Vite approach of dealing with DOM manipulation. I bumped into this a number of times now (I'm not using the mentioned frameworks).

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

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