bug: A horizontal scroll bar appears with long white space before the text
Closed this issue · 15 comments
Describe the bug
A horizontal scroll bar appears with long white space before the text
To Reproduce
Steps to reproduce the behavior:
-
Go to: input
-
type:
text
Expected behavior
Trim white space
Screenshots
If applicable, add screenshots to help explain your problem.
Package version
- stream-chat-react:
v12.2.2
- stream-chat-css:
- stream-chat-js:
v8.40.9
hey @vihan85 , thank you for the report. Is this an issue for the UI of demo application?
Hi @MartinCupela, this issue occur on demo, I founded it on v11.23.6
hey @vihan85 , thank you for the report. Is this an issue for the UI of demo application?
@MartinCupela
yes, I found it on your demo.
Hi @MartinCupela this issue confirmed?
So the issue description confused me, as I was typing characters and spaces, but the actual thing to type is not shown correctly by the Github markdown parser. After setting the issue description to edit mode I have seen the below:
But if you take a look at how GH parses the markdown, it is the same as the message. I cannot therefore consider this a bug
@MartinCupela it just show example, you can test that on you demo page
Yes, but it behaves as expected. See how it is rendered in this issue description
You are quoting something, so the white spaces will not be trimmed
I just typing: test. do not quote
Quoting in markdown is putting character >
at the beginning of the line. That is what your issue description contains. Your last message is confusing.
oh That wasn't my intention, I just wanted it to appear similar to the demo
Screen.Recording.2024-11-14.at.9.25.28.PM.mov
test
The same thing happens in GitHub as you can see above in this message
This is not a bug
You can watch the video below.
Why does a horizontal scroll bar appear instead of a line break?
Can you support line breaks like when entering a consecutive string that doesn't contain spaces?
Social.Messaging.Demo.-.Example.Messaging.App.mp4
Hey @vihan85 , the whitespace is not trimmed, because that is how MD is interpreted by the parser. It is by design. If you would like to change the behavior, I encourage you to provide your custom remark plugins. The guide is available here:
You can take an inspiration from an existing plugin in the SDK: