We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Attempt to add a warning tip using the !> tag, running over multiple lines with a nested list, for example:
!>
!> * list item 1 !> * list item 2 !> * list item 3
The warning tag does not allow sub elements to be rendered correctly because it uses paragraph tags instead of div tags.
Currently, if you put !> tags over multiple lines, you get the following output:
Or if you add line breaks:
Ideally, this should work similar to the > blockquote tag where it still allows you to put lists and other elements nested below it:
>
This can be achieved by rendering it inside <div> tags instead of <p> tags as follows:
<div>
<p>
N/A
The text was updated successfully, but these errors were encountered:
Good catch, thanks! A fix shouldn't be too hard.
Sorry, something went wrong.
Any chance this will be fixed in the near future?
Successfully merging a pull request may close this issue.
Bug Report
Steps to reproduce
Attempt to add a warning tip using the
!>
tag, running over multiple lines with a nested list, for example:What is current behaviour
The warning tag does not allow sub elements to be rendered correctly because it uses paragraph tags instead of div tags.
Currently, if you put
!>
tags over multiple lines, you get the following output:Or if you add line breaks:
What is the expected behaviour
Ideally, this should work similar to the
>
blockquote tag where it still allows you to put lists and other elements nested below it:This can be achieved by rendering it inside
<div>
tags instead of<p>
tags as follows:Other relevant information
N/A
Please create a reproducible sandbox
N/A
Mention the docsify version in which this bug was not present (if any)
N/A
The text was updated successfully, but these errors were encountered: