UI: Share one tooltip root across Dag card run-state badges - #69927
Conversation
|
Thanks for helping with the dags list performance! |
Backport failed to create: v3-3-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 018f0c2 v3-3-testThis should apply the commit to the v3-3-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
|
Depends on #67242 marked for 3.4.0. Updating the milestone of this PR to 3.4.0 as well. |
related: #69609
Each Dag card renders 4 run-state badges (added in #67242), each with its own Tooltip.Root. On a page of 50 cards that's up to 200 independent tooltip controllers, even though only one tooltip can be active at a time.
This applies the same pattern #69681 used for the recent-runs bar: one shared Tooltip.Root per card, with each badge as a Tooltip.Trigger, and the hovered badge's content resolved through Tooltip.Context. No visual change is expected.
Demo
Screen.Recording.2026-07-15.at.11.07.54.PM.mov
Was generative AI tooling used to co-author this PR?
{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.