(BTW, for the intent owner: only one LGTM needed for this intent.) On Wed, Mar 12, 2025 at 9:50 AM Alex Russell <slightly...@chromium.org> wrote:
> LGTM1 > > I continue to be concerned that we are proliferating these declarative > forms without any object model. I'd like to see an OM for speculation > rules, import maps, and other similar designs. Has this come up in your > discussions with the TAG? > > Best, > > Alex > > On Thursday, March 6, 2025 at 11:42:03 AM UTC-5 Huanpo Lin wrote: > >> The previous email didn't include the section of Goals for >> experimentation. >> I'm sending this email as a follow-up. >> >> Goals for experimentation >> >> To evaluate how the prerendering target_hint support works on real sites >> before shipping it by default. We will be evaluating performance, >> stability, and correctness, and any other feedback the sites have when they >> use this feature. >> >> Kind regards >> >> On Thu, Mar 6, 2025 at 2:42 PM Chromestatus < >> ad...@cr-status.appspotmail.com> wrote: >> >>> Contact emails nhir...@chromium.org, robert...@chromium.org >>> >>> Explainer >>> https://github.com/WICG/nav-speculation/blob/main/triggers.md#window-name-targeting-hints >>> >>> Specification >>> https://wicg.github.io/nav-speculation/speculation-rules.html >>> >>> Summary >>> >>> This extends speculation rules syntax to allow developers to specify the >>> target_hint field. This field provides a hint to indicate a target >>> navigable where a prerendered page will eventually be activated. For >>> example, when _blank is specified as a hint, a prerendered page can be >>> activated for a navigable opened by window.open(). The field has no effect >>> on prefetching. The specification allows this field to accept any strings >>> that are valid as navigable target name or keyword as the value, but this >>> launch supports only one of "_self" or "_blank" strings. If the hint is not >>> specified, it's treated like "_self" is specified. >>> >>> >>> Blink component Internals>Preload>Prerender >>> <https://issues.chromium.org/issues?q=customfield1222907:%22Internals%3EPreload%3EPrerender%22> >>> >>> Search tags speculationrules <http:///features#tags:speculationrules>, >>> prerendering <http:///features#tags:prerendering> >>> >>> TAG review https://github.com/w3ctag/design-reviews/issues/931 >>> >>> TAG review status Issues addressed >>> >>> Risks >>> >>> >>> Interoperability and Compatibility >>> >>> None >>> >>> >>> *Gecko*: Neutral ( >>> https://github.com/mozilla/standards-positions/issues/620) >>> >>> *WebKit*: No signal ( >>> https://github.com/WebKit/standards-positions/issues/54) >>> >>> *Web developers*: No signals >>> >>> *Other signals*: >>> >>> WebView application risks >>> >>> Does this intent deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>> None >>> >>> >>> Goals for experimentation >>> >>> >>> >>> Ongoing technical constraints >>> >>> None >>> >>> >>> Debuggability >>> >>> DevTools supports speculation rules: >>> https://developer.chrome.com/blog/debugging-speculation-rules/ >>> >>> >>> Will this feature be supported on all six Blink platforms (Windows, Mac, >>> Linux, ChromeOS, Android, and Android WebView)? No >>> >>> Android WebView doesn't support speculation rules yet. >>> >>> >>> Is this feature fully tested by web-platform-tests >>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>> ? Yes >>> >>> https://wpt.fyi/results/speculation-rules/prerender >>> >>> >>> Flag name on about://flags >>> enable-speculation-rules-prerendering-target-hint >>> >>> Finch feature name Prerender2InNewTab >>> >>> Requires code in //chrome? False >>> >>> Tracking bug https://issues.chromium.org/issues/40234240 >>> >>> Estimated milestones >>> Origin trial desktop first 135 >>> Origin trial desktop last 140 >>> Origin trial Android first 135 >>> Origin trial Android last 140 >>> >>> Link to entry on the Chrome Platform Status >>> https://chromestatus.com/feature/5162540351094784?gate=5081681619058688 >>> >>> 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 visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/496c3c78-b691-4106-8ea2-5c72c2bb29ffn%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/496c3c78-b691-4106-8ea2-5c72c2bb29ffn%40chromium.org?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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-0BoBJCmWg%2BzeVjP5P-tbmHN%2BjjbGD9u6uKr3c1ww5zw%40mail.gmail.com.
