In some places like thread prefixes as illustrated in the post of @magdi5 above, it even brakes single words, hence I am not sure if white-space property will be any helpful. For instance we have this issue in our forum for a thread prefix "انٹرویو" which has no space in it, but breaks into "انٹرو" and "یو".This looks like it might be a browser bug -- I can see it locally and I actually just noticed it in a location in the style properties as well. This is a situation where it really shouldn't wrap. May need to look at a test case to possibly report, but will move this to bugs in the meantime.
You can workaround it by applying white-space: nowrap; to the callToActionSpan style property (search for that in the ACP search).
Google Chrome Version 35.0.1916.153 (Ubuntu 14.04), I can still see this happening, no change observed.This was certainly a browser bug, but I'm not actually seeing it happen any more (Chrome 35.0.1916.153). It may be sorted now.
Anyone still see it with the latest Chrome?
To me it looks like the problem has something to do with ligature based fonts. Recently Google Chrome has introduced a lot of issues related to rendering ligature based complex script languages (potentially in RTL languages). There is a problem in which it cannot calculate the width of the ligatures properly and accumulates the empty space in the beginning of the line that results in an indented line when it is rendered. I was able to fix that issue by using a CSS property "-webkit-font-feature-settings: "ccmp" 0;", which is essentially instructing the browser not to apply CCMP feature of the font.Since this isn't happening to me any more, can someone link to a page where I could see it? (Preferably as a guest, but if you want to send me a test login that works too.)
If it is happening with Tahoma then my assumption that it only happens with ligature based fonts is not right. Considering Tahoma as a very common font, I think this needs some sort of fix if possible.I notice that this issue dose not appear in our testing website.
The only difference (that I noticed) between testing and live websites is the "font-family"
snapshot from testing website:
View attachment 77468
snapshot from live website:
View attachment 77469
Removing Tahoma from font-family in the body fixed the issue.
I returned back Tahoma, and sent you PC with links, so you can see the issue.
We use essential cookies to make this site work, and optional cookies to enhance your experience.