- From: Martin Thomson <notifications@github.com>
- Date: Tue, 08 Oct 2024 15:42:56 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 8 October 2024 22:42:59 UTC
Hi @kjmcnee, we were discussing this and we're not following the reasoning. Why do you see rel=opener as the right approach, rather than by keying on target=\<anything>? That a new window with target= will not be discoverable is surprising. That navigations will end up in a different process is similarly surprising. Obviously rel=noopener breaks that link and enables moving to a new process, but an explicit rel=opener as an explicit request to stay in the same BCG seems like it has some awkward consequences. Concretely, what do we stand to lose if we insist that new windows stay in the same group? Are there performance numbers that motivate having a process switch? Maybe WebKit's behavior is evidence that the costs are acceptable. That might trade-off back-forward performance for straight-up loading performance, but I'm curious about what the real cost would be. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/979#issuecomment-2400943661 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/979/2400943661@github.com>
Received on Tuesday, 8 October 2024 22:42:59 UTC