passleAug 14, 2023
Dying to implement out of order streaming to show loading states while streaming the rest of the document and add mpa view transitions. App-like experience entirely by just streaming some html from a service worker.
Show threadSasha FirsovAug 27, 2023

@passle
"Dying to implement out of order streaming".

I am still looking for "unified" streaming Interface ( as in TypeScript ) for DOM transformation. String in - parser - diff -merge.. kind of streaming processing can (imo should) be using same interface API . If it is unified, the implementation polifills and shims would make a platform a "evolutionary architecture " wise.
Please share if you come over such APIs

Show threadpassle
@Suns That sounds kind of what swtl does, except theres no diffing, because it happens in a SW (there is no dom). Can you be more explicit in what you think it should do exactly?
Aug 27, 2023 at 3:48pmElk
Show threadSasha FirsovAug 27, 2023

@passle , I an thinking on #w3ctag proposal for steaming based processing for #DeclarativeWebApplication / #DeclarativeCustomElement the template html has to be read, parsed, dependent tree stream merged( including data) , template+data rendered in stream, diff to page DOM created, and finally merged. All steps should be using this unified API for bypassing own input to output.

Delivering results while the 1st tier yet to be completed.

Show threadpassleAug 27, 2023
@Suns This just sounds like you want ssr for custom elements?
Show threadSasha FirsovAug 27, 2023

@passle , ssr is just a one tier. I am thinking on multiple tiers where Hydration is applicable.

And Custom Element is not a goal. Rather #DeclarativeWebApplication