[yuseok89]

#69619 made the Dags list remount every row whenever the list auto-refreshed with active runs, since the cell renderers were recreated together with the run state counts. Besides the flicker fixed in #74426, I found that the remount also closed the dialog opened from the pause toggle at the next refresh, so it could close before the user chose between pausing and draining. #74426 fixed both by moving the renderers to module level.

This adds tests to keep the regression from coming back. They render the Dags list with a running Dag, let it auto-refresh with changing run state counts, and check both symptoms in the card and table views.

• The rows are not remounted after a refresh.
• The pause or drain dialog opened from the toggle stays open across a refresh.

Each test fails on the code before #74426 and passes on main. The tests lower auto_refresh_interval to one second, so each one takes about 1.2s.

related: #69619, #74426

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  • Claude Code (Opus 5.5)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[bbovenzi]

Looks good. Let's just rebase

[github-actions]

Backport successfully created: v3-4-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-4-test