Maybe a weird side-effect, but think of web.whatsapp.com: You have the tab open already, open a new tab, enter web.whatsapp.com, so you'll get an action item in the omnibox to switch to the already open tab - but with prerendering this leads to web.whatsapp.com showing you've opened the site in a new tab (even though you didn't - it got prerendered), making the "switch to already open tab" suggestion useless. Is this something site maintainers will have to fix or on the chromium side? (Prerendering interaction with already open tabs)
[email protected] schrieb am Mittwoch, 16. Februar 2022 um 17:51:00 UTC+1: > On Wednesday, February 16, 2022 at 6:48:00 PM UTC+2 [email protected] > wrote: > >> hey folks, >> >> Looking at this in API OWNERS this morning, I wasn't able to see an >> obvious developer opt-out. The spec and explainer talk about letting the >> server opt-out, but it appears that the primary way that would happen is >> aborting a response. This is a potentially expensive and surprising for >> servers. Has there been any thought about supporting a response header that >> would allow a response document to opt into, e.g., only prefetch behavior >> but not prerendering? >> > > correct, it's still in discussion, and feedback is very welcome! > https://github.com/WICG/nav-speculation/issues/138 > > >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7ec8c1d3-e443-441b-882e-73e0511de8f3n%40chromium.org.
