The feature itself doesn't break links in that way at all.
If, and only if,
(1) a website uses strict cookies on a cookie
(2) the website assumes that cookie (1) is always available for 'valid requests'
(3) the website assumes that 'valid requests' (2) include top-level navigation events (such as typing the website's url into the browser bar)
then any behaviour that relies on the existence of that cookie will break in some situations.
That is, only a naive use of this feature will cause breakage. Worthwhile knowing about for developers, but in an ideal world would never cause issues for users.
In an ideal world there would be a solution without this shortfall, but it seems like an almost necessary feature due to how some cross origin requests are made (by spawning a new window etc).
If, and only if,
(1) a website uses strict cookies on a cookie
(2) the website assumes that cookie (1) is always available for 'valid requests'
(3) the website assumes that 'valid requests' (2) include top-level navigation events (such as typing the website's url into the browser bar)
then any behaviour that relies on the existence of that cookie will break in some situations.
That is, only a naive use of this feature will cause breakage. Worthwhile knowing about for developers, but in an ideal world would never cause issues for users.
In an ideal world there would be a solution without this shortfall, but it seems like an almost necessary feature due to how some cross origin requests are made (by spawning a new window etc).