kaxil opened a new pull request, #1667:
URL: https://github.com/apache/airflow-site/pull/1667

   On docs pages, text on the same line as the sticky footer row (scroll-to-top 
button on the left, "Suggest a change" pill on the right) cannot be selected. 
The row is a full-width flex container, and it captures the mouse across the 
whole line even though it is transparent.
   
   #1503 fixed this by giving the container `pointer-events: none` and 
re-enabling the buttons inside it. On docs pages the same element also carries 
the `fade-target` class (from #1162), whose rule set `pointer-events: auto`. 
Both selectors are one class and `_suggest-change.scss` is imported after 
`_base-layout.scss`, so the `auto` won and quietly undid the fix on every 
Sphinx docs page.
   
   This removes the `pointer-events: auto` from `.fade-target`. The container 
keeps `pointer-events: none`, the child `button, a` rule still makes both 
buttons clickable, and the hover-hide rule for the TOC is unchanged.
   
   Verified in headless Chromium against the live `stable/index.html` by 
drag-selecting across the button row. Before: the container is the hit target 
along the whole row and nothing gets selected. After: hit-testing lands on the 
page content and the line selects normally (the code block's copy button also 
appears on hover now, since hover reaches it too).
   
   Before, no selection:
   
   
![before](https://raw.githubusercontent.com/kaxil/airflow-site/84bcfc4642bac65f2aadb50e303b79b4c4458208/suggest-change-pointer-events/suggest-change-before.png)
   
   After, the line under the button row selects:
   
   
![after](https://raw.githubusercontent.com/kaxil/airflow-site/84bcfc4642bac65f2aadb50e303b79b4c4458208/suggest-change-pointer-events/suggest-change-after.png)
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Fable 5.1)
   
   Generated-by: Claude Code (Fable 5.1)


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