Hi team,
I'm working on a web application where I open a second tab using window.open() to host another part of my own app — for example, an excel sheet in a separate tab while keeping the main design interface open in the original one. Both tabs are from the same origin, but intentionally separated for UX and performance reasons. To improve security and memory efficiency, I use noopener and noreferrer when opening the new tab. This helps avoid process and memory linkage between the tabs, especially with modern site isolation and performance models. However, one critical interaction I’d like to preserve is the ability for the child tab to bring focus back to the original tab (its opener), for example after onClick button action. Without opener access, calling window.opener.focus() is no longer possible. In short, I’m looking to achieve all three of the following: - Open a new tab for my own app using window.open() - Use noopener and noreferrer for memory isolation - Still allow the child tab to focus the parent tab Right now, there doesn't seem to be a secure and reliable way to do this. I understand the restrictions exist for good reason, but it would be helpful. This would help developers build secure multi-tab interfaces without compromising UX. I’d appreciate any insights into whether this is already being discussed or considered as part of platform evolution. Thanks for your time and for your work on web platform security and performance. Best regards, Kavan Gondalia -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/71a62bc1-4a9f-4bc4-9199-906a649bf0cdn%40chromium.org.
