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
{{ message }}
This repository has been archived by the owner on Feb 13, 2022. It is now read-only.
I've an issue with the custom tag that will be injected if markdown extra is enabled. This inevitability is an issue when working with css grid as it breaks the layout. Support for custom tags is limited, srcsetplugin is anyway not a valid custom tag without a dash, and it causes issues with css preprocessing and linting when I try to add a display:contents; to it, taking it out of the render path.
What is the purpose of the tag, isn't there a more standardised option or can it be disabled?
The text was updated successfully, but these errors were encountered:
<srcsetplugin> and </srcsetplugin> should not appear in the frontend code but be removed by the plugin unless i made an error with my markdown extension that handles that. it "should" not collide with markdown and markdown extra.
what is your markdown setup? any config values in that regard? any other plugins that alter markdown?
I've an issue with the custom tag that will be injected if markdown extra is enabled. This inevitability is an issue when working with css grid as it breaks the layout. Support for custom tags is limited,
srcsetplugin
is anyway not a valid custom tag without a dash, and it causes issues with css preprocessing and linting when I try to add adisplay:contents;
to it, taking it out of the render path.What is the purpose of the tag, isn't there a more standardised option or can it be disabled?
The text was updated successfully, but these errors were encountered: