-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
RE: Large concurrent text cutoff for more than one line #53 #65
Comments
Hi @RaphaelBaskerville , |
Have the same issue. There is Germany in the real world... ( |
Hi @ivanouski and @RaphaelBaskerville , may I have a screenshot and what result are you expected? Does the word be cut off is acceptable? For example the word If can, then I will plan this feature. |
could perhaps this be implemented as a configurable option? something like
the result of the code above would be to try and fit as many characters as is possible if This way the behaviour is retained for those that want it split by word, but also supports those that want it split by characters? Our use case is that we are trying to show some strings that developers use to name entities. and those are end-user-defined, so they could do anything from "my very descriptive name for an entity" to "my_very_descriptive_name_for_an_entity" and in the second case - we're not able to show anything at all, which is sad |
For those that stumble upon this later. If you're trying to truncate a single long line of text with no spaces, an alternative is to just use CSS:
make sure your width is set to whatever makes sense in your context |
I'm having the same issue. We have titles that sometimes use underscores instead of spaces. We can't do much about the titles since our customers enter those themselves. It would be nice to be able to support |
I am having the same issue as described in:
Issue #53
I noticed that your last comment said that it was fixed and to use 0.13.0. but I have tested with it and It seems like long words are still being cut-off in narrow containers.
Is there any plan to fix this @ShinyChang?
Or perhaps I am not using it correctly...
The text was updated successfully, but these errors were encountered: