On Wed, Mar 6, 2024 at 12:04 PM Noam Rosenthal <nrosent...@chromium.org> wrote:
> > > On Wed, Mar 6, 2024 at 10:55 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Mon, Mar 4, 2024 at 5:36 PM Vladimir Levin <vmp...@chromium.org> >> wrote: >> >>> Contact emailsvmp...@chromium.org, nrosent...@chromium.org >>> >>> Explainer >>> https://github.com/WICG/view-transitions/blob/main/document-render-blocking.md#blocking-element-id >>> >> >> Thanks for the explainer. It's very useful!! >> >> The explainer mentions console warnings in case authors included an ID >> that wasn't encountered, resulting in waiting for the fill document. >> Was this implemented? >> > > It was not, good catch! Opened > https://issues.chromium.org/issues/328279707. > > >> Will render blocking also happen in cases where no transition took place? >> (e.g. on landing pages) >> > > Correct, this feature is not specific to view transitions. It can be used, > for example, as a replacement for the existing practice of loading a hidden > page and showing it using JS at a particular point. It allows a tradeoff > between smoothness and speed, regardless of view transitions. > OK. In this case it might be interesting to think through current use-cases for such initial page hiding (e.g. A/B testing comes to mind) and see how they could be implemented using this and whether this would be a positive change. Did such thinking take place? -- 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/CAOmohSJZ5OdTwqgv3SVH8XEc%2BucvJL5iZ2sZe9ZivhqS2dJNXA%40mail.gmail.com.
