![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Context Menu: "This Frame -> Open in New Tab" does not preserve the private browsing container
If I right click on an iframe when browsing in a container tab, and select "This Frame -> Open in New Tab", the new tab is not in the same container as the source tab. In fact it is not in any container.
Whereas when middle-clicking on a normal link to open it in a new tab, the new tab is in the same container as the source tab.
Is this a bug? Seems like a bug to me. Surely we would want the new tab to use the same container as the source tab?
Усі відповіді (2)
Does this vary based on the address of the site in the frame?
For example, if I Shift+right-click an embedded YouTube video frame > This Frame > Open Frame in New Tab, the embedded video opens in the page's container instead of its regularly assigned container. (On my page here: https://www.jeffersonscher.com/gm/google-hit-hider/)
If you check This Frame > View Frame Info, is there a standard URL or a data URI or about: address, etc.?
Sorry, it seems to only impact ServiceNow websites. Every other iframe example I have tried seems to work just fine. I think it might be a problem when the iframe is inside a shadow DOM.