Repository navigation
Fix square corner on fully filled dashboard History bars - #73543
Merged
Merged
Conversation
choo121600
requested review from
bbovenzi,
guan404ming,
pierrejeambrun,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
September 22, 2026 12:15
bbovenzi
approved these changes
Sep 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Dashboard History section renders each state as a two-segment bar, with each segment rounding its outer corners.
When a state reaches 100%, the remaining segment collapses to 0% width, leaving the filled segment with square right corners.
This makes the filled segment round its right corners when
remainingWidth === 0, so a fully filled bar keeps all four corners rounded while partially filled bars remain unchanged.before
After
Was generative AI tooling used to co-author this PR?
claude opus 4.8
{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.