reveal.js: Slide Notes timer doesn't work

When I open the Slide Notes browser page (pressing s) the timer doesn’t start. I’m using Chromium and I’m getting this error in the console

Uncaught ReferenceError: Reveal is not defined
    at getTimings (notes.html:484)
    at setupTimer (notes.html:541)
    at handleConnectMessage (notes.html:387)
    at notes.html:354

this doesn’t happen in the standard view. I’m using the latest git version with Chromium 59. I’m initializing the presentation like this:

    <script src="../reveal.js/lib/js/head.min.js"></script>
    <script src="../reveal.js/js/reveal.js"></script>
    <script>
      Reveal.initialize({
          dependencies: [
            // Interpret Markdown in <section> elements
            { src: '../reveal.js/plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
            { src: '../reveal.js/plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
            { src: '../reveal.js/plugin/notes/notes.js', async: true }
          ],
          slideNumber: false
      });
    </script>

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 17 (3 by maintainers)

Most upvoted comments

@kuncevic, are you opening demo.html directly in the browser (file:/// URL), or running a local web server?

As per the documentation on speaker notes, notes only work from a web server.

Took a while but I found out how to reproduce that error. It happens when you press the ‘S’ to open the speaker view, and then go back to the main window and press the ‘S’ key again while the popup is still open in the background.

It’s not happening when first opening the speaker view in any browser that I’ve tested.

Wasn’t able to find a way to fix it yet though.

@bnjmnt4n @hakimel

This bug is still present. I can reproduce it e.g. on https://revealjs.com/ You may reconsider to open this issue again.

It happened for me the first time I pressed s as well. Using incognito mode fixed it for me, so I think it was some kind of caching issue (I had upgraded from a previous release). Killing all cache didn’t seem to help, but restarting Chrome did.

To me it does happen the first time I press s.