choo121600 opened a new pull request, #73541:
URL: https://github.com/apache/airflow/pull/73541
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
## Summary
In the Dag run grid view, after paging back to older runs, there was no
visible way to return to newer runs. The "newer runs" and "jump to latest"
buttons were positioned just beyond the right edge of the horizontally
scrollable bar strip.
Because the strip is right-anchored to the scrollport, the button group
ended up outside the visible area and also introduced a phantom horizontal
scrollbar.
## Cause
The newer/reset button group was absolutely positioned with a negative right
offset (right={-6}) relative to the right-anchored strip, placing it beyond the
scrollport edge where it was clipped.
## Change
Keep the button group inside the strip by using a non-negative right inset.
To make room for the buttons without overlapping the newest run bar, reuse
the existing right-edge ScrollbarSpacer and widen it from 16px to 32px only
when the pager is shown.
## Before
https://github.com/user-attachments/assets/60848ba0-4eab-4def-953f-2d9a3ce5edb6
## After
https://github.com/user-attachments/assets/46d1c3a5-f703-4d9c-808f-79e32b52522b
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
https://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [x] Yes (please specify the tool below)
claude opus 4.8
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#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](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
