Describe the bug
Progressive slides should work more robustly (or at all?) in 3.0-dev. This should mean:
When a <!-- stop --> comment is encountered, we cut a new slide (this is how it's currently implemented)
HOWEVER, in 3.0-dev, we also need to be able to keep track of the current stack
More context: tokens with the new markdown library don't have nested children (usually) - open and close tokens are completely separate. We'll have to keep track of how to correctly unwind.
This is likely easiest to do by:
adding an unwind stack to the Context
updating the render_all functions to:
push the correct <token>_close tokens to the Context's unwind stack
pop from the unwind stack as the real <token>_close tokens are observed.
Once this is implemented, we should be able to add <!-- stop --> comments anywhere, even in tables, and have everything render/unwind correctly.
Describe the bug Progressive slides should work more robustly (or at all?) in 3.0-dev. This should mean:
<!-- stop -->comment is encountered, we cut a new slide (this is how it's currently implemented)This is likely easiest to do by:
render_allfunctions to:<token>_closetokens to the Context's unwind stack<token>_closetokens are observed.Once this is implemented, we should be able to add
<!-- stop -->comments anywhere, even in tables, and have everything render/unwind correctly.