ionic-team / ionic-team/ionic-framework

bug: ion-datetime performance lag when used in popover/modal with other layout components (no min/max set)

Abierto
#30,398 2 comentarios 0 reacciones 0 asignados Ver en GitHub
ionitron: needs reproduction
Lenguaje dominante
TypeScript
Estrellas
52.7k
Forks
13.3k
Merge medio
1 d 15 h
PR fusionados (30 d)
51

Descripción

**Prerequisites/Environment**
- Ionic version: @ionic/angular 8.5.5
- Angular project - v19.2
- Using ion-datetime inside a popover or modal.
- Not setting min or max on the datetime (by design).
- This issue is consistently observed on desktop browsers (eg. Chrome/Edge).
- Not yet tested on mobile devices.

**Description**
We are observing significant performance lag (4–6s delay) when opening the ion-datetime component via a popover or modal on pages that contain heavy layout components, such as:
- ion-grid, ion-row, ion-col
- Custom components (lib-*)
- ion-content scrollable layout

The lag is most noticeable when no min or max is set on the datetime — which is intentional in our case.

**Steps to Reproduce**
1. Add ion-datetime inside a popover
2. Use it on a page that includes a full ion-grid or ion-modal with custom lib components
3. Do not set min or max on the datetime
4. Click the trigger button to open the popover

**Observed Behavior**
- The datetime popover takes a noticeable time (up to 5 seconds) to render
- During this time, the UI appears frozen or unresponsive
- The lag disappears when used on a minimal page without any custom components and only the button and ion-datetime.

**Expected Behavior**
- ion-datetime should open promptly in a popover regardless of page layout
- Performance should not degrade when used without min/max range

**Code sample**
```
`



Pick a Date






`
```

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.