Skip to content

Conflict with wavedrom #430

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.

Sign up for GitHub

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

Jump to bottom
Closed
rubyu opened this issue Mar 19, 2018 · 1 comment
Closed

Conflict with wavedrom #430

rubyu opened this issue Mar 19, 2018 · 1 comment

Comments

@rubyu
Copy link

rubyu commented Mar 19, 2018

I am trying to use docsify with wavedrom, but since wavedrom uses JSON format in <script type="WaveDrom">...snip...</script> as the setting value for a graph, docsify seemed to be failed evaluating it and seemed to be dead😢
Is this a bug? Or else is there any way to avoid this issue?

snapcrab_noname_2018-3-19_23-52-11_no-00
@rubyu
Copy link
Author

rubyu commented Mar 20, 2018

Sorry for bothering you, this issue was solved. I found the root cause of this problem that executeScript processes only the first <script> element in .markdown-section.
I inserted the script <script>WaveDrom.ProcessAll();</script> on the head of the md file, and then it worked fine.

@snyk-bot snyk-bot mentioned this issue Jun 17, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rubyu @QingWei-Li