Thank you! On Wed, Apr 6, 2022 at 11:55 PM Yoav Weiss <yoavwe...@chromium.org> wrote:
> LGTM to extend the experimentation to M102, given the API changes with > regards to the BroadcastChannel. > Please note that this experiment is reaching the typical time limits of > OTs, and experimentation beyond that would require significant > justification and 3 LGTMs. > > On Wed, Apr 6, 2022 at 4:48 PM Hiroki Nakagawa <nhir...@chromium.org> > wrote: > >> Hi Yoav, >> >> The requested timeline is from M101 to M102. The current timeline is from >> M94 to M100, and the experiment is still running >> >> On Wed, Apr 6, 2022 at 11:39 PM Yoav Weiss <yoavwe...@chromium.org> >> wrote: >> >>> What's the requested timeline for experimentation? Is the experiment >>> currently still running? >>> >>> On Mon, Apr 4, 2022 at 4:42 PM Hiroki Nakagawa <nhir...@chromium.org> >>> wrote: >>> >>>> Contact emails >>>> >>>> nhir...@chromium.org, navigation-...@chromium.org >>>> >>>> Explainer >>>> >>>> This feature: >>>> <https://chromestatus.com/admin/features/launch/5355965538893824/This%20feature:%20https://github.com/jeremyroman/alternate-loading-modes/blob/main/same-origin-explainer.md> >>>> https://github.com/WICG/nav-speculation/blob/main/same-origin-explainer.md >>>> >>>> This trial: >>>> https://github.com/WICG/nav-speculation/blob/main/same-origin-chrome-origin-trial.md >>>> >>>> Larger project: >>>> <https://chromestatus.com/admin/features/launch/5355965538893824/Larger%20project:%20https://github.com/jeremyroman/alternate-loading-modes/blob/main/README.md> >>>> https://github.com/WICG/nav-speculation/blob/main/README.md >>>> >>>> Specification >>>> >>>> https://wicg.github.io/nav-speculation/prerendering.html >>>> >>>> Design docs >>>> >>>> >>>> https://docs.google.com/document/d/1P2VKCLpmnNm_cRAjUeE-bqLL0bslL_zKqiNeCzNom_w/edit?usp=sharing >>>> >>>> Summary >>>> >>>> Prerendering loads a web page before it is needed, so that when the >>>> actual navigation to that page occurs, it can be shown instantly. See the >>>> previous >>>> intent >>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/tcbtZoQIlvI/m/K26gVfbUAQAJ> >>>> for details of the feature. >>>> >>>> >>>> >>>> <Updates from the previous extension> >>>> >>>> - A partner finished an experiment and confirmed that latency on their >>>> service is reduced by 45%. >>>> >>>> - The intent-to-ship for Omnibox prerendering >>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/ogegRwcRlcs/m/abCQpUFpAQAJ> >>>> is approved. This is a different prerendering trigger, but the underlying >>>> prerendering system and the specifications are common. We’re also going to >>>> send the intent-to-ship for speculation rules prerendering soon. >>>> >>>> - We’d like to extend the experiment to address issues raised in the >>>> intent-to-ship for Omnibox prerendering (e.g., BroadcastChannel in >>>> prerendered pages) and verify changes merged after the last milestone of >>>> the experiment (M100). >>>> >>>> Blink component >>>> >>>> Internals>Preload>Prerender >>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Internals%3EPreload%3EPrerender> >>>> >>>> TAG review >>>> >>>> https://github.com/w3ctag/design-reviews/issues/667 >>>> >>>> TAG review status >>>> >>>> Pending >>>> >>>> Risks >>>> >>>> No updates. See the previous intent >>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/tcbtZoQIlvI/m/K26gVfbUAQAJ> >>>> . >>>> >>>> Goals for experimentation >>>> >>>> To evaluate how the prerendering feature works on real sites before >>>> shipping it by default. This is a large feature and it's risky to ship >>>> without trying it first on real sites. We will be evaluating performance, >>>> stability, and correctness, and any other feedback the sites have when they >>>> use this feature. >>>> >>>> Reason this experiment is being extended >>>> >>>> We’d like to extend the experiment to address issues raised in the >>>> intent for Omnibox prerendering and verify changes merged after the last >>>> milestone of the experiment (M100). >>>> >>>> Ongoing technical constraints >>>> >>>> None >>>> >>>> Debuggability >>>> >>>> Currently DevTools does not work for prerendered pages. On activation, >>>> DevTools must be closed and reopened in order to inspect the page. We have >>>> plans to add DevTools support for prerendering. A meta bug for this work is >>>> at https://crbug.com/1217029. >>>> >>>> >>>> >>>> As a very small support, prerendered pages are visible in >>>> chrome://process-internals. Also final results of prerendering are shown in >>>> chrome://histograms. >>>> >>>> >>>> >>>> <Updates from the previous extension> >>>> >>>> We started implementing the DevTools support for prerendering. As a >>>> first step, we will expose prerender activation/cancellation result to the >>>> DevTools (https://crbug.com/1249776) >>>> >>>> Will this feature be supported on all six Blink platforms (Windows, >>>> Mac, Linux, Chrome OS, Android, and Android WebView)? >>>> >>>> No. This feature is only supported on Android at first. As the feature >>>> is a cross-cutting one, where almost all of Chrome's features must be >>>> potentially taught about prerendered pages, we are starting with a >>>> single platform and expanding later. >>>> >>>> Is this feature fully tested by web-platform-tests >>>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> >>>> ? >>>> >>>> Partially tested [cs >>>> <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/speculation-rules/prerender/>]. >>>> We’re now upstreaming wpt_internals/ tests [doc >>>> <https://docs.google.com/document/d/1XqdlrYdPbLLEfJfjQE1IK0I5Elj_2uiGaK5aUGYc1CU/edit?usp=sharing> >>>> ]. >>>> >>>> Flag name >>>> >>>> Prerender2 >>>> >>>> Requires code in //chrome? >>>> >>>> False >>>> >>>> Tracking bug >>>> >>>> https://crbug.com/1126305 >>>> >>>> Launch bug >>>> >>>> https://crbug.com/1167987 >>>> >>>> Estimated milestones >>>> >>>> The initial experiment timeline: M94 to M98 [I2E >>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/3JwGNnqH3QI/m/Ey103Q-yAQAJ> >>>> ] >>>> >>>> The previous extended timeline: M99 to M100 [I2EE >>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/tcbtZoQIlvI/m/K26gVfbUAQAJ> >>>> ] >>>> >>>> Requested extension timeline: M101 to M102 >>>> >>>> Link to entry on the Chrome Platform Status >>>> >>>> https://chromestatus.com/feature/5355965538893824 >>>> >>>> >>>> >>>> This intent message was generated by Chrome Platform Status >>>> <https://chromestatus.com/>. >>>> >>>> -- >>>> 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 blink-dev+unsubscr...@chromium.org. >>>> To view this discussion on the web visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABj5diMsJyJSf%3DtaygFWCa7n-ZADocAYU%2ByUHsfcP%2BnHP3F2sg%40mail.gmail.com >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABj5diMsJyJSf%3DtaygFWCa7n-ZADocAYU%2ByUHsfcP%2BnHP3F2sg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- 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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABj5diOW_-DohG6JK%2BaUgd8Ew7t1e0pkSTriE%2B1vjxXMnYLSCQ%40mail.gmail.com.
