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
In comments to script Feedback posts, in order to force a line return using Markdown, in 'Preview' tab you have to put two empty spaces at the end of a line, but when posting the comment these two spaces become two separate line returns #752
Comments
I believe this was because it was reading the incorrect format for the preview (it was seeing the choice for other, invisible forms on the page). Should be fixed now. |
Also, the OP's issue unfortunately still occurs: I just posted a comment in https://greasyfork.org/en/scripts/12179-greasyfork-bull-filter/discussions/58257#comment-150905 I believe 2 spaces should be needed for newlines in Discussions, not 1, |
This is fixed now. |
I don't really understand the original issue. Are you referring to spaces (like with the spacebar) or line breaks (with Enter)? When I try it, I don't see any difference between preview and the end result. |
What I mean is that if I use 1-space (yes with the spacebar) in the end of each line, In details:
i.e. here are my 1-spaces: and here is how they are rendered in the 'Preview' tab: (as expected) and here is how they are rendered after I submit it: (as newlines) |
@JasonBarnabe
That is, in Discussions, If I use this Markdown: Markdown
I'm getting: Output in 'Preview' (1 line return, as expected)
Output in submitted post/comment (2 line returns)
|
I don't see that. I get one line break. Can you post a discussion in the forum with just that and I can take a look? I suspect it may be a CR vs LF thing. |
Here, my latest comment in https://greasyfork.org/en/scripts/12179-greasyfork-bull-filter/discussions/59057#comment-152364 How it's displayed in the 'Preview' tab: (the two-space trailing spaces are at the arrows): |
In addition to the above comment links I took the liberty of making this separate test post+comment in "Greasy Fork Feedback" I also made this script Feedback post and it also works ok. BUT, the issue occurs when I wrote a comment for a script Feedback post (for a a script of mine) : Markdown: Great to hear.
I'm glad you find it useful. |
OK, so the problem was when the page previously rendered an HTML comment, the HTML config was bleeding into the Markdown config. It should be fixed now and the extra whitespace is gone. |
Thank you for fixing this. |
Maybe it's related: And i don't understand how list are applied, seems very confusion. Here a screenshot of the problem (before i try to "fix" it for my userscript: |
I've noticed the following in the redesigned discussion while using Markdown (when creating a discussion post/comment):
If I use 2 spaces for a newline e.g.
then in the Preview tab it shows it as expected, i.e.
but when I submit the post/comment, it takes each space for a newline, making up two newlines in total:
The text was updated successfully, but these errors were encountered: