-
-
Notifications
You must be signed in to change notification settings - Fork 889
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
Wrapping issue on long lines #17
Comments
Maybe to use RichText to display text? |
|
Hi any news about this issue? |
@kevinApplaud Pull request #37 is a proposed solution to the issue. |
Any news on this? |
Sorry, I've been busy with finals. Will get to this soon! |
Hi there! Any news on this issue? |
Wouldn't it be better to use TextSpans in p elements instead of Text Widgets? |
@The-Redhat see #17 (comment) above |
@ianrothmann Sorry, I have other projects for both work and school taking up a lot of my time that have priority over this project. I promise I will get to this, but it may be a couple weeks still. |
Ok thanks @Sub6Resources. I hope you can fix this bug as soon as possible! |
Pull request #37 has been merged and version 0.9.0 released. This provides a fix for the text wrapping issue by creating a parser that uses To use the new
This issue will be closed and a new issue opened in regards to the default parser still having the issue. |
any workaround? I need to use customRender (to render iframes), so can't use RichText UPD. my workaround is to render all elements manually |
@bgpastukh You can also use version 1.0.0-pre.1 which has built in support for iframe rendering and wraps lines correctly as well. |
How can I fix this on version 1.1.1, while there is no parameter useRichText? |
Since 1.x there is only one parser/renderer. No need to choose. If you have an issue with long text, you may open a new issue. |
I have a problem like in #388, I thought that this can help. Any suggestions? |
@amanokerim Please file a new issue, with a minimal example to reproduce the problem. Thanks! |
Reported in #9 by @chusmf:
The text was updated successfully, but these errors were encountered: