If a word is the last word inside a tag, it ends with non-ascii utf8 characters and there are no characters after it before the end-tag, the word may be cut into two lines. Draw the window narrower with the test case (it may be necessary to enlarge the font if the browser window can't be narrow enough). This has been confirmed with QWebView and also in Arora browser on Linux and Windows, but couldn't be repeated with KHTML or Safari, i.e. it's probably Qt specific. The test case is below, it's also attached: <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <span>doesn't happen: not divided</span> <div>happens: äöäöäöääöå</div> <span>happens: abcdefgäöå</span> <div>doesn't happen: ölööööäå.</div> <div>doesn't happen: not divided</div> <span>happens: äöäöäöääöå</span> <div>happens: abcdefgäöå</div> <span>doesn't happen: ölööööäå.</span> <span>happens? dfabcöbcadf</span> <span>happens? tabcöäbcaa</span> <span>happens? öäbcaadfd</span>
Created attachment 44072 [details] testcase Did the previous attachement come in? Anyways, the text in the original report text was a bit outdated, here is the final one...
Please follow the QtWebKit bug reporting guidelines when reporting bugs. See http://trac.webkit.org/wiki/QtWebKitBugs Specifically: - The 'QtWebKit' component should only be used for bugs/features in the public QtWebKit API layer, not to signify that the bug is specific to the Qt port of WebKit http://trac.webkit.org/wiki/QtWebKitBugs#Component - Add the keyword 'Qt' to signal that it's a Qt-related bug http://trac.webkit.org/wiki/QtWebKitBugs#Keywords
Reproduced on Linux with 4.6, r55658.
https://bugs.webkit.org/show_bug.cgi?id=34470 Bug 34470 - [Qt] Non-ASCII line breaking doesn't work properly (seen at www.mail.ru) https://bugs.webkit.org/show_bug.cgi?id=32019 ? Bug 32019 - [Qt] last word inside a tag is divided into two lines if it ends with non-ascii characters I looked at both these errors and was not able to reproduce either. Neither has been commented on in almost a year. I suspect these were duplicates that have been fixed along the way. Unless someone can verify these are still a problem, I think these should be resolved as WorksForMe.
My bet is that has been fixed by Pierre in https://bugs.webkit.org/show_bug.cgi?id=31076 *** This bug has been marked as a duplicate of bug 31076 ***