Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

class="fragment" in speaker notes reveal.js #1394

Closed
FRidh opened this issue Jul 2, 2014 · 3 comments
Closed

class="fragment" in speaker notes reveal.js #1394

FRidh opened this issue Jul 2, 2014 · 3 comments

Comments

@FRidh
Copy link

FRidh commented Jul 2, 2014

It's possible to use Markdown in speaker notes for reveal.js, e.g.:

<div class="notes">
- item a
- item b
</div>

However, when using lists like this in combination with the setting -incremental results in

<aside class="notes">
<ul>
<li class="fragment">item a</li>
<li class="fragment">item b</li>
</ul>
</aside>

This in effects requires extra clicks to proceed to the next slide.

Removing class="fragment" solves the problem.

@jgm jgm closed this as completed in 05a5b4e Jul 10, 2014
@pperez
Copy link

pperez commented Dec 22, 2014

I'm using pandoc 1.13.2 but i still have this issue.
Here is the source file i'm using https://gist.github.com/pperez/481f687a6ebb0250f97e#file-laravel-md and the resulting html file https://gist.github.com/pperez/481f687a6ebb0250f97e#file-laravel-html
Generated the html using this command:
pandoc -t revealjs --incremental --mathjax -V theme=night -s /Users/pperez/Documents/slides/content/laravel.md -o /Users/pperez/Documents/slides/output/laravel.html

Am i doing something wrong?

jgm added a commit that referenced this issue Mar 15, 2015
This closes #1394, which actually wasn't fixed by the earlier commit.
This ensures that lists in speaker notes don't add "fragment" classes,
which can cause additional keypresses to be needed to advance a slide.
@vser1
Copy link

vser1 commented Jan 4, 2018

This bug is still present in pandoc 1.19.2.4 (sorry have no current access to the 2.x branch). Shall I reopen issue #2006, or maybe open a new bug once confirmed on 2.x?

For further reference, my current workaround is to quote the list as suggested in the Manual

@mb21
Copy link
Collaborator

mb21 commented Jan 4, 2018

open a new bug once confirmed on 2.x

yes, with a minimal reproducible example...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants