jaymasiwal commented on PR #38792: URL: https://github.com/apache/superset/pull/38792#issuecomment-4127441703
Hi everyone, I’ve been working on improving frontend UI behavior in Superset, particularly around dropdown rendering and container handling. Recent contributions: * #37985 (merged) – restored full name display in Action Logs * #38792 – improved `getPopupContainer` handling to avoid double scrollbars while preserving modal behavior * #38659 – explored dropdown rendering inconsistencies and edge cases While working on these, I encountered recurring issues related to: * inconsistent container handling across components * portal-based rendering causing test and UI inconsistencies * difficulty maintaining predictable behavior in modal vs non-modal contexts I’ve also worked through fixing related Jest test failures (especially around portal-based dropdowns and async rendering), which highlighted gaps in current testing patterns. I’m planning to propose a GSoC (Google Summer of Code 26) project focused on: * standardizing container rendering logic * improving Explore view performance * refactoring control components for consistency and testability Before finalizing the proposal, I wanted to ask: Does this direction align with current frontend priorities in Superset? Are there specific areas in Explore view or control components that would benefit most from this effort? Would really appreciate any feedback. Thanks! -- 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]
