Skip to content

Fix layout overflow issue in DAG Details Logs tab#64013

Open
Revanth14 wants to merge 1 commit intoapache:v2-11-stablefrom
Revanth14:fix-log-header
Open

Fix layout overflow issue in DAG Details Logs tab#64013
Revanth14 wants to merge 1 commit intoapache:v2-11-stablefrom
Revanth14:fix-log-header

Conversation

@Revanth14
Copy link

Description

Fixes the details panel where the header, breadcrumb, and action buttons disappear when task logs (or any tab content) is longer than the viewport.

Problem

Improper height handling in nested flex containers caused tab content (such as Logs) to expand beyond its intended bounds. When content exceeded the viewport height, the page-level layout scrolled in a way that hid the header and action controls.

Fix

  • Applied correct flex layout rules (flex={1}, minH={0})
  • Restored explicit height="100%" where required for Graph and Gantt rendering
  • Ensured contained scroll behavior without affecting page-level scroll

Testing

  • Manual verification in Logs, Graph, and Gantt tabs
  • Frontend tests passing
  • Static checks passing

Before

before image 1 before image 2

After

after image1

After scrolling the full page

after image 2

Fixes #63934

@boring-cyborg
Copy link

boring-cyborg bot commented Mar 20, 2026

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

  • Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
  • In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
  • Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
  • Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
  • Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
  • Be sure to read the Airflow Coding style.
  • Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
    Apache Airflow is a community-driven project and together we are making it better 🚀.
    In case of doubts contact the developers at:
    Mailing List: dev@airflow.apache.org
    Slack: https://s.apache.org/airflow-slack
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant