summaryrefslogtreecommitdiff
path: root/lib/epub.js/examples/index.html
diff options
context:
space:
mode:
Diffstat (limited to 'lib/epub.js/examples/index.html')
-rw-r--r--lib/epub.js/examples/index.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/epub.js/examples/index.html b/lib/epub.js/examples/index.html
index 707b1d8..2aa2ece 100644
--- a/lib/epub.js/examples/index.html
+++ b/lib/epub.js/examples/index.html
@@ -88,7 +88,7 @@
<li><a href="swipe.html">Swipe</a><p>
This example includes a function in the script to link "swipe" events on touchscreens, particularly mobile devices, to navigate forward and back. Note that swipes do not work in Chrome Desktop even if you turn on device emulation in the "inspect" toolbar. </p></li>
<li><a href="input.html">Open from File</a><p>
- Allows you to select an epub file from your local computer that gets rendered in the browser. As of 5/14/2019 only the cover renders.</p></li>
+ Allows you to select an epub file from your local computer that gets rendered in the browser.</p></li>
<li><a href="renderless.html">Renderless</a><p>
The name for this example is misleading since the book certainly does render. What's unique in this example is that the book's table of contents is read in and a list of sections in developed, then each section is rendered as it is called for by a section.render() call, but there's no master book.renderTo() call. Functionlly this seems exactly the same as 1) and 3).</p></li>
<li><a href="hooks.html">Hooks</a><p>