diff options
| author | Mario Botsch | 2019-04-23 23:28:05 +0200 |
|---|---|---|
| committer | Mario Botsch | 2019-04-23 23:28:05 +0200 |
| commit | 1f5fb971d4a6cf6ab153a2484a440f80e24a1400 (patch) | |
| tree | 611d0a13d84029dd8ec59fcbfcfe8b3505fafa7a | |
| parent | a16b71a981e9385627959273bb4e910e1d502c92 (diff) | |
Fix plugin documentation
Mention that reveal.js will wait for the Promise of a plugin's init()
function only when the plugin is loaded non-async. The init functions
of plugins that are loaded as async dependencies are called after
reveal.js has dispatched the 'ready' event.
| -rw-r--r-- | README.md | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -1268,6 +1268,7 @@ Reveal.addEventListener( 'ready', () => console.log( 'Three seconds later...' ) Reveal.initialize(); ``` +For plugins that are loaded as [dependencies](#dependencies), reveal.js will wait for the fullfillment of their init Promise only for the *non-async* plugins. If the init method does _not_ return a Promise, the plugin is considered ready right away and will not hold up the reveal.js startup sequence. ### Retrieving Plugins |