ARBS-23 opened a new issue, #42510: URL: https://github.com/apache/superset/issues/42510
### Bug description When editing a chart and opening **View query**, clicking **View in SQL Lab** triggers a redirect confirmation dialog. That confirmation dialog is rendered **behind** the "View query" modal instead of on top of it, so the user cannot interact with it without first closing the query modal. ### To Reproduce 1. Log in to Superset. 2. Open any chart and enter **Edit Chart** mode. 3. Make any change to the chart (so unsaved changes exist). 4. Open the chart menu (`...`) → **View query**. 5. In the "View query" modal, click **View in SQL Lab**. ### Expected behavior The redirect confirmation dialog should appear **in front of** the "View query" modal, with the correct focus trap and overlay stacking, so the user can confirm or cancel navigation to SQL Lab. ### Actual behavior The redirect confirmation dialog opens, but it is visually and functionally **behind** the "View query" modal. The query modal remains on top and blocks interaction with the confirmation dialog. ### Screenshots/recordings <img width="1920" height="911" alt="Image" src="https://github.com/user-attachments/assets/5771029d-5817-4d9b-9eb3-598ef62284e7"; /> ### Superset version 6.1.0 ### Python version 3.11 ### Node version 16 ### Browser Chrome ### Additional context This looks like a modal stacking / `z-index` issue between: - the **View query** modal in the chart editor, and - the **unsaved-changes / redirect confirmation** dialog shown when navigating to SQL Lab. Likely areas to inspect: - modal `zIndex` / portal stacking order in the chart editor - whether the redirect confirmation uses a lower stacking context than nested chart modals - Ant Design `Modal` / `getContainer` usage when multiple modals are open ### Checklist - [x] I have searched Superset docs and Slack and didn't find a solution to my problem. - [x] I have searched the GitHub issue tracker and didn't find a similar bug report. - [x] 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]
