zachliu opened a new issue, #63934:
URL: https://github.com/apache/airflow/issues/63934

   ### Apache Airflow version
   
   2.11.X
   
   ### If "Other Airflow 3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   The buttons are beheaded or even disappeared all together along with dag 
name and task name when the logs fill up the log window (aka when it is longer 
enough to scroll).
   
   <img width="360" height="88" alt="Image" 
src="https://github.com/user-attachments/assets/11d8613f-5cf0-469f-8ecf-e6795d9bc024";
 />
   
   <img width="720" height="132" alt="Image" 
src="https://github.com/user-attachments/assets/d51cc59c-c771-4b78-a58b-971a37a1c71d";
 />
   
   
https://github.com/user-attachments/assets/ccdb3ed7-a4fd-4e2b-baf3-15319c468316
   
   
https://github.com/user-attachments/assets/69d5f5ee-2889-4111-a698-c0c9b7acc272
   
   ### What you think should happen instead?
   
   The headers and buttons should always be visible regardless of log length.
   
   ### How to reproduce
   
   1. Go to a task that is able to generate logs longer than one browser window
   2. Select the "Logs"
   3. Resize (drag the middle divider) the logs window and grid view if need be 
   
   ### Operating System
   
   LM 21.3 with docker python:3.12-slim-bookworm
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to