Exploring incremental rendering as the default #481
Description
This issue is to explore what it would take to make incremental rendering the default. I'll be testing in some projects and writing notes here on things like bugs, UX, etc.
Overview
Incremental rendering is really 2 things. One is a mutation stream renderer and the other is a reattacher. I would rate the stability of these things as:
- Mutation Stream: 8/10 - (fairly stable, still find bugs when trying in new apps)
- iframe Reattacher: 4/10 - Not so stable.
- Styles not currently showing in the iframe.
- If HTML is wrong in any way the reattachment happens too quickly.
Issues
- - Currently we do not support H2 (
require('http2')). Instead we use a fork of node-spdy which is not really maintained. We should definitely switch to the build-in module. - - We should make it easier to debug IR instructions: Make it easier to debug incremental rendering instructions #483
- - The iframe idea causes images to be loaded twice (if uncached): Incremental rendering causes images to be loaded twice #401
UX
- -
--certand--keyarguments are required to start an H2 server. Would it maybe be possible to include a default key/cert for development?
Apps
place-my-order
- - Initial styles are not part of the iframe overlay.
- - Bug
- - Detachment doesn't happen
