marking it "test" CL is submitting Yoav Weiss (@Shopify) <yoavwe...@chromium.org> schrieb am Fr. 19. Sep. 2025 um 15:06:
> > > On Fri, Sep 19, 2025 at 2:57 PM Noam Rosenthal <nrosent...@chromium.org> > wrote: > >> >> >> On Fri, Sep 19, 2025, 1:46 PM Yoav Weiss (@Shopify) < >> yoavwe...@chromium.org> wrote: >> >>> >>> >>> On Fri, Sep 19, 2025 at 2:26 PM Helmut Januschka <hjanusc...@gmail.com> >>> wrote: >>> >>>> @nrosent...@chromium.org - got you. should i do a follow up CL or >>>> revert and reland? >>>> >>> >>> I believe a follow up is sufficient >>> >>> >> >> Agreed! >> >> One think to look out for before we ship this is whether it regresses >> FCP/LCP for some sites. >> >> eg if the page relies on module scripts to load the LCP, having >> additional render frames in between scripts might slow it down. >> > > Yeah, definitely something to measure as part of the Finch. > > >> >> Hopefully it's a net positive and worth a try! >> >> <nrosent...@chromium.org> schrieb am Fr. 19. Sep. 2025 um 14:13: >> >>> On Fri, Sep 19, 2025 at 12:16 PM Helmut Januschka <hjanusc...@gmail.com> >>>>> wrote: >>>>> > >>>>> > Hey folks, >>>>> > >>>>> > We’ve recently landed a fix on issue where multiple deferred scripts >>>>> where all executing in the same task. That’s something developers have >>>>> been >>>>> complaining about, as a source of long tasks in sites that have many >>>>> different deferred scripts from various sources. >>>>> >>>>> Thanks for working on this! This is great! >>>>> > >>>>> > The fix is behind the experimental SeparateDeferModuleScriptTasks >>>>> flag at the moment and +Scott Haseley is planning to Finch it to see its >>>>> impact on INP in the wild. >>>>> >>>>> I think this should be behind "test", as per this guideline: >>>>> >>>>> >>>>> https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/renderer/platform/RuntimeEnabledFeatures.md#:~:text=If%20your%20feature%20could%20be%20reasonably%20expected%20to%20cause%20compat%20issues%2C%20please%20keep%20it%20marked%20no%20status%20or%20status%3A%22test%22%20%5B4%5D%2C >>>>> >>>>> If your feature could be reasonably expected to cause compat issues, >>>>> please keep it marked no status or status:"test" >>>>> >>>>> I think this can be reasonably expected to cause compat issues, though >>>>> I hope it doesn't! >>>>> >>>>> > There’s still an open question of whether the HTML spec needs to be >>>>> changed, or if “spin the event loop” allows for the tasks to be queued. >>>>> We’d appreciate opinions on that front. >>>>> >>>>> There is a discussion on this here: >>>>> https://github.com/whatwg/html/issues/6230 >>>>> The conclusion so far is that both the old behavior and the new >>>>> behavior are spec-compliant. >>>>> >>>> -- >>>> 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/CAFmjHKS2d6NpkoQnFDh1zhYD%2BnVYPGVjOr0R%2BTX_we_J6R%3D62g%40mail.gmail.com >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFmjHKS2d6NpkoQnFDh1zhYD%2BnVYPGVjOr0R%2BTX_we_J6R%3D62g%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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFmjHKQ%2BCqkCxefX5zcCUcELtC_f8U6b4woZZx%2BM_9VvzynYyw%40mail.gmail.com.
