-
Notifications
You must be signed in to change notification settings - Fork 94
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
Attachments are formatted together with the next paragraph #2873
Comments
I suspect attachments are inline elements and therefor form part of the next paragraph. I think they should be block elements in their own right. |
@eneiluj Do you have an idea about this? |
Seems it is related to #2868 |
The reason is that we intentionally set
I'm not sure about the implications of switching to @max-nextcloud, @juliushaertl and @vinicius73 curious about your thoughts 😊 |
As we are using complex render strategies to render attachments, it can't be handled inline mode. |
I agree. I wonder though, what implications switching from inline to block mode has. Given that markdown-it creates inline images, would that result in modified markdown source code after opening and closing documents with images? |
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Use markdown-it-image-figures to render standalone images inside `<figure>` elements instead of `<p>` when markdown source gets parsed into HTML. This allows to treat images as block elements by TipTap. Also keep support for inline images to not break markdown files that have inline images. Fixes: #2873 Signed-off-by: Jonas <jonas@freesources.org>
Describe the bug
When changing the format below an attachment it also affects the attachment itself.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The attachment stays the way it is. Formatting only affects the section below
Screencast
Bildschirmaufzeichnung vom 08.09.2022, 11:23:23.webm
The text was updated successfully, but these errors were encountered: