I'm not sure what you mean by pre-rendered html? The basic idea of the SD polyfill is that each shadow host gets an associated renderer. When the logical dom is changed in a way that effects a renderer this renderer gets invalidated. Invalidated renderers get scheduled to be updated using requestAnimationFrame. You can also force all invalidated renderers to update synchronously by reading a property that depends on layout information, such as offsetWidth for example.
When a renderer is rendered it produces the composed tree (visual dom) which is what the browser uses to paint. On Wed, Feb 5, 2014 at 3:48 PM, Oleksii Khliupin <[email protected]> wrote: > Hi, > > Please, could someone to help with a topic. > I need to understand the workflow of rendering process in case when the > native shadow dom is not available. > The most important place - When the root element is replaced with > pre-rendered html? > > thank you. > > Follow Polymer on Google+: plus.google.com/107187849809354688692 > --- > You received this message because you are subscribed to the Google Groups > "Polymer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/polymer-dev/2772b7f3-cc81-439c-83d0-6d8f254837b8%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- erik Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAJ8%2BGogpWOmmwGMijeEi4eX3cpsw-0hbqvdAQBdDrCy42MXaUg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
