88bc143431
Currently styles are rendered to the root component element, which ensures they're cleaned up automatically
when the client application is bootstrapped. This is less than ideal as progressive rendering can cause HTML
to be rendered before the CSS is loaded, causing flicker.
This change returns to rendering <style> elements in the <head>, and introduces a mechanism for removing
them on client bootstrap. This relies on associating the server and client bootstrap. Another way to think
of this is that the client, when bootstrapping an app, needs to know whether to expect a server rendered
application exists on the page, and to identify the <style> elements that are part of that app in order
to remove them.
This is accomplished by providing a string TRANSITION_ID on both server and client. For most applications,
this will be achieved by writing a client app module that imports BrowserModule.withServerTransition({appId: <id>}).
The server app module will import this client app module and therefore inherit the provider for
TRANSITION_ID. renderModule[Factory] on the server will validate that a TRANSITION_ID has been provided.
|
||
|---|---|---|
| .. | ||
| @angular | ||
| angular1_router | ||
| benchmarks | ||
| benchmarks_external | ||
| e2e_util | ||
| payload_tests/hello_world/ts | ||
| playground | ||
| rollup-test | ||
| empty.ts | ||
| es6-subset.d.ts | ||
| system.d.ts | ||
| tsconfig.json | ||
| types.d.ts | ||