pedro-cf opened a new issue, #63714:
URL: https://github.com/apache/airflow/issues/63714

   ### Apache Airflow version
   
   2.11.X
   
   ### If "Other Airflow 3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   After upgrading from Airflow 2.11.0 to 2.11.2, in the DAG Graph view, the 
cursor no longer changes to a pointer (cursor: pointer) when hovering over a 
task node box. The cursor only changes when hovering directly over the task 
label/title text inside the box.
   
   In 2.11.0 the cursor changed to a pointer over the entire task node, giving 
a clear visual affordance that the box is clickable.
   
   ### What you think should happen instead?
   
   The cursor should change to a pointer when hovering anywhere over the task 
node box, as it did in 2.11.0. This is important UX feedback indicating the 
node is interactive/clickable.
   
   ### How to reproduce
   
   1. Deploy Airflow using the official Docker image 
apache/airflow:2.11.2-python3.12
   2. Open any DAG in the Graph view
   3. Hover the mouse over a task node box (but not over the task label text)
   4. Observe: cursor remains as default arrow
   5. Hover over the task label text inside the box
   6. Observe: cursor changes to pointer
   
   ### Operating System
   
   Ubuntu 24.04.3 LTS
   
   ### 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