htcnokia opened a new issue, #43352:
URL: https://github.com/apache/superset/issues/43352

   ### Bug description
   
   
   ### **Problem Statement**
   
   When interacting with large Pivot Tables in Superset, horizontal and 
vertical scrolling causes the top-left intersection header area (which defines 
the column/row structure context) to scroll out of view. This makes it 
difficult to maintain context regarding what data is currently displayed, 
especially across large datasets requiring wide/long scrolling.
   
   ### **Proposed Solution**
   
   Implement sticky positioning using CSS (e.g., `position: sticky`, `z-index`, 
`top`, `left` rules) or a lightweight JavaScript solution within the Pivot 
Table (v2) chart visualization plugin.
   
   Specifically:
   
   * **Top-left intersection cell(s):** Stick to both `top: 0` and `left: 0` 
with a higher `z-index` so they remain visible during both horizontal and 
vertical scrolling.
   * **Column headers (`<thead>`):** Stick to `top: 0` during vertical 
scrolling.
   * **Row headers / First column(s):** Stick to `left: 0` during horizontal 
scrolling.
   
   ### **Use Case / Value**
   
   * **Enhanced UX & Usability:** Users can continuously track context when 
navigating large Pivot Tables without repeatedly scrolling back to the top-left 
corner.
   * **Standardized Data Exploration:** Aligns Superset's Pivot Table 
experience with standard spreadsheet tools (e.g., Excel/Google Sheets freeze 
panes).
   
   ### **Environment Information**
   
   * **Superset Version:** 6.1.0
   * **Visualization:** Pivot Table / Pivot Table v2
   
   ---
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.11
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [ ] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [ ] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [ ] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to