max / quasi

A link can say the reader is leaving, not just going elsewhere Destination::External always opened a tab, so a same-tab navigation out of the app was unsayable. The measured consumer is MNW's custom-pages host: u.makenot.work serves a creator's page with a platform strip on it, and every link in that strip goes to the apex in the same tab, because going to the apex is the whole point of the strip. Said as External all three would open tabs, which is a satellite document refusing to let go of a reader who asked to leave. Destination::Leaving is the other half. The split is intent and the mechanism stays the renderer's, which is the call panel placement and the toast clock both got: a tab is window management, and what a renderer cannot infer from an address alone is which kind of leaving this is. A terminal with no tabs follows both the one way it can and is not wrong. rel="noopener noreferrer" on both rather than only on the tab. noreferrer is what stops the Referer a same-tab navigation still sends, neither is a cost, and a branch would be a second thing to get right. A redirect header treats the two alike, since a page that has already navigated has nothing to keep aside.