anthony-joyce opened a new issue, #37720:
URL: https://github.com/apache/airflow/issues/37720

   ### Apache Airflow version
   
   2.8.1
   
   ### If "Other Airflow 2 version" selected, which one?
   
   2.8.2
   
   ### What happened?
   
   When zoomed out node titles do not shorten with three dots like seen in the 
release notes example.
   
   ![Screenshot 2024-02-26 at 12 32 39 
PM](https://github.com/apache/airflow/assets/18553670/cf5dfee1-c734-41bf-ab28-b7752ac89079)
   
   When zoomed in, node subtitles migrate out of the margins.
   
   ![Screenshot 2024-02-26 at 12 32 48 
PM](https://github.com/apache/airflow/assets/18553670/695b2515-877a-4dca-b522-628e2fc7d7f8)
   
   
   
   ### What you think should happen instead?
   
   I expect to see similar functionality and scaling seen in the release notes 
examples.
   
   <img width="684" alt="302757308-2d56ab70-ea94-4408-a70b-5e8aab710707" 
src="https://github.com/apache/airflow/assets/18553670/9e295149-722c-4366-9856-cab7bea73746";>
   
   
![302764993-b2e79714-b9b2-44b2-a5da-3a0d88822fa5](https://github.com/apache/airflow/assets/18553670/75bb77af-4e89-487f-b42a-1a024a759d19)
   
   
   
   ### How to reproduce
   
   Simple steps. Upgrade to Airflow 2.8.2 ---> airflow db migrate ---> started 
webserver and scheduler ---> checked Graph UI.
   
   ### Operating System
   
   CentOS 7
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   Cent OS 7 stand alone Apache Airflow installation using it's own Python 
environment.
   
   ### Anything else?
   
   Sustained issue.
   
   ### 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