[blink-dev] Intent to Ship: Omnibox Prerendering

Contact emails loading-...@chromium.org, noam.j.rosent...@gmail.com Component Internals>Preload>Prerender Explainer https://github.com/WICG/nav-speculation/blob/main/ua-initiated-prerendering.md Spec https://wicg.github.io/nav-speculation/prerendering.html Discussion about upstreaming into H

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

Hi, Following the previous discussion on this thread, I wanted to share a couple of updates: - We have updated the web.dev article with the current state and some useful information for web develo

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

FWIW, the comment in the HTML spec triage was positive feedback to have a spec for this. The current spec proposal clearly is missing still quite a few cases (is the idea really that one can use BroadcastChannel with prerendered page? and the webidl annotation behaves rather oddly) So it is surpris

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

On 2/11/22 07:20, Kouhei Ueno wrote: Contact emails loading-...@chromium.org , noam.j.rosent...@gmail.com Component Internals>Preload>Prerender Explainer https://github.com/WICG/nav-speculation/blob/main/ua-initiated-pre

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

On Fri, Feb 11, 2022 at 11:53 AM Olli Pettay wrote: > FWIW, the comment in the HTML spec triage was positive feedback to have a > spec for this. > The current spec proposal clearly is missing still quite a few cases (is > the idea really that one can use BroadcastChannel with prerendered page? >

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

I agree with Domenic that it's great to see this kind of feature, that was traditionally unspecified, getting some clearer developer visibility and a spec. While there may still be missing pieces, this seems like a good start. I'm looking forward to further spec discussions that would hopefully lea

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

On Saturday, February 12, 2022 at 7:11:29 AM UTC+2 yoav...@chromium.org wrote: > I agree with Domenic that it's great to see this kind of feature, that was > traditionally unspecified, getting some clearer developer visibility and a > spec. While there may still be missing pieces, this seems

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

On Mon, Feb 14, 2022 at 11:33 AM Noam Rosenthal wrote: > > > On Saturday, February 12, 2022 at 7:11:29 AM UTC+2 yoav...@chromium.org > wrote: > >> I agree with Domenic that it's great to see this kind of feature, that >> was traditionally unspecified, getting some clearer developer visibility >>

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

I created an issue specifically for the BroadcastChannel discussion: https://github.com/WICG/nav-speculation/issues/141 We'd love to hear if there are other issues with restrictions (or other) that need addressing! Browse/open at https://github.com/WICG/nav-speculation/issues On Monday, February

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

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 fo

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

On Wednesday, February 16, 2022 at 6:48:00 PM UTC+2 sligh...@chromium.org 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 wa

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

On Sun, Feb 20, 2022 at 12:10 PM Jacob G wrote: > 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

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

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

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

Hi, While we are discussing, we would like to continue the incremental roll out of the feature to non-Stable channels. As of now, we are testing out the feature on 60% of Dev/Canary channels, and 60% of Beta channels. The rollout is limited to Android Chrome (limitation of the current implementati

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

Hey Kouhei, Thanks for highlighting that there's an opt-out option now. I'm a little concerned that it requires servers to avoid sending a response at all, forcing an early decision by the infrastructure rather than allowing pages requested this way to be prefetched by not prerendered (by, e.g.

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

Yes, there are plans for such a header, join the discussion here: https://github.com/WICG/nav-speculation/issues/138 However so far fleshing out its details was not deemed a blocker for releasing prerender - a simple "all or nothing" opt-out seemed sufficient as a first step. On Wednesday, Marc

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

LGTM1. The two issues I considered blocking were Alex's concerns around opt-out, and the BroadcastChannel integration. It seems to me like there's still discussion to be had on even better solutions than y'all have landed on for both (headers in the one case, more explicit integration with Broadca

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

LGTM2 On 3/21/22 8:12 AM, Mike West wrote: LGTM1. The two issues I considered blocking were Alex's concerns around opt-out, and the BroadcastChannel integration. It seems to me like there's still discussion to be had on even better solutions than y'all have landed on for both (headers in the

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

LGTM3 On Mon, Mar 21, 2022 at 2:16 PM Mike Taylor wrote: > LGTM2 > > On 3/21/22 8:12 AM, Mike West wrote: > > LGTM1. > > The two issues I considered blocking were Alex's concerns around opt-out, > and the BroadcastChannel integration. It seems to me like there's still > discussion to be had on e

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

When are you planning to ship? Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com | 816-678-7195 *If an API's not documented it doesn't exist.* On Mon, Mar 21, 2022 at 6:18 AM Yoav Weiss wrote: > LGTM3 > > On Mon, Mar 21, 2022 at 2:16 PM Mike Taylor > wrote: > >> LGTM2 >> >> On