Element Attributes only support simple markdown, no nested inline elements
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 72.3k
- Forks
- 17k
- PR merge metrics
- No merged PRs in 30d
Description
Consider:
<section data-markdown>
<script type="text/template">
#intro to svg
- Vector images <!-- .element: class="fragment" -->
- A permutation of `XML` <!-- .element: class="fragment" -->
</script>
</section>
This results in A permutation of XML just showing up onSlideLoad, ignoring the intended fragment order.
I tried <!-- li: class="fragment" --> but that just displays all list items onSlideLoad.
This applies for anything in markdown that would create html inside of that line (italic, bold, pre, etc).
I'd like for a way to denote fragments in markdown for elements that contain inline elements.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the provided section with data-markdown and inline markdown such as code, emphasis, or bold, then trace how markdown-generated elements receive fragment attributes. Done means inline elements inside list items preserve the intended fragment order instead of appearing on slide load.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100