-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Markdown Preview update sometimes breaks down in the restored preview #345
Comments
Same problem here. Marp for VS Code v1.5.1 |
This comment was marked as outdated.
This comment was marked as outdated.
I finally found out an accidental collision of minified global variable, between Marp's script for preview and VS Code's preview script. In the context of morphdom, used by VS Code for incremental updation of DOM, a global variable On the other hand, Marp's minified preview script also has defined Fortunately it is easy to fix: Set |
Version of Marp Tool
Marp for VS Code v1.5.1
Operating System
Windows
Environment
How to reproduce
Expected behavior
Replaces the current Markdown preview to the updated contents.
Actual behavior
The outdated preview contents will keep from the second updation, and new contents will insert to the last of preview.
Additional information
I guess Marp extension is causing failed updation of the preview because could not reproduce that if disabled Marp extension.
It is especially reproducible when edited Markdown at the same timing as showing restored preview. (At that time, I think script for VS Code's preview has been loaded, but a contribution script from Marp may not be loaded yet)
The text was updated successfully, but these errors were encountered: