By User on Thursday, 20 June 2019
Posted in General Issues
Replies 7
Likes 0
Views 528
Votes 0
Hello. There is nothing critical, but I'm interesting, what do you think - should be it fixed in package or it looks normal as designed and should be customised by webmaster.

At the moment css file has this:
#es .es-leader-context__info {
word-break: break-all;
}
And last RealName letter is moved on next lin (letter looks lonely). More at the screenshot.

May be it should be "break-word"?

Thanks.
The reason why we added this break-all styling is because if the name very long, the name will not fit in the module, you can check my screenshot here : http://take.ms/s4iug .

By the way, you can apply this following css under your template custom css file :


body #es.mod-es-leader .es-leader-context__info {
word-break: inherit !important;
}
·
Thursday, 20 June 2019 12:41
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello. If I try to use "word-break: inherit !important;" it's realy cause problem.

But if use "word-break: break-word !important;" it start to look OK with long and normal names (without lonely letter).

May be it should be "word-break: break-word" as default (in core css-file)? Thanks.
·
Friday, 21 June 2019 03:03
·
0 Likes
·
0 Votes
·
0 Comments
·
It seems like word-break: break-word css attribute will do the trick, we will update this into the core.
·
Friday, 21 June 2019 10:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello. I just noticed that this issue was not fixed in 3.1.4.
I'd like to remind in case it's lost.
·
Saturday, 29 June 2019 00:46
·
0 Likes
·
0 Votes
·
0 Comments
·
Can I know how to replicate this on your site?
·
Saturday, 29 June 2019 10:40
·
0 Likes
·
0 Votes
·
0 Comments
·
CSS-file still contain this:
#es .es-leader-context__info {word-wrap: break-word;}
and somitemes we can see one letter on next line, but not
word-break: break-word !important;


To replicate I just edited sourse code (change username to "Хороший динозавр") and look to result. Example at the screenshot. Thanks.
·
Saturday, 29 June 2019 14:30
·
0 Likes
·
0 Votes
·
0 Comments
·
Okay, I saw the issue now, I will inform again to our developer regarding to include the fix in next release version.
·
Sunday, 30 June 2019 12:26
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post