You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This plugin seems to break it's output when attempting to embed the following gist when noscript is enabled, and jekyll-commonmark is used as the markdown renderer
This doesn't appear to happen on other posts where I have gists embedded.
My theory is that maybe because the gist ends in a triple backtick codeblock (possibly with no newline?), that that may be breaking something within this plugin, that then flows on to breaking how commonmark parses/renders things?
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
This plugin seems to break it's output when attempting to embed the following gist when
noscript
is enabled, and jekyll-commonmark is used as the markdown renderer{% gist 0xdevalias/e8bb28726a37854606ad %}
_config.yml
Rendered snippet
In particular, the end part of the rendered
noscript
seems to be getting itself confused, and then ends up breaking the output:This doesn't appear to happen on other posts where I have gists embedded.
My theory is that maybe because the gist ends in a triple backtick codeblock (possibly with no newline?), that that may be breaking something within this plugin, that then flows on to breaking how commonmark parses/renders things?
The text was updated successfully, but these errors were encountered: