GNOME Bugzilla – Bug 766822
TextView: spaces acting as non-breaking whitespace if :left- or :right-margin is set
Last modified: 2018-05-02 17:10:43 UTC
In using the GTK Twitter-Client corebird(http://corebird.baedert.org/), I encountered a problem with the way spaces are treated by GTK: they seem to act as non-breaking white space that prevent text from wrapping around/between words (See conversation on Twitter https://twitter.com/corebirdclient/status/734826338222231552) Expected behaviour would be (as mentioned there, that text wraps around words when 'wrap mode' is 'word-char'.
works fine here; a testcase would be needed to figure out what is going on
Created attachment 328418 [details] Testcase This seems to happen whenever left-margin *and* right-margin are set. Without the g_object_set call here, everything works fine.
+1 encountering the same issue here, also in Corebird's DM implementation. It makes it cumbersome to type a message of more than a few words, as the window gets wider and wider to fit the text instead of the text wrapping.
I think this may be fixed? Haven't had this issue when I was using the latest Ubuntu Mate.
yes, it works in my version of Corebird on Gnome on Antergos as well
We worked around it in Corebird. This bug is not fixed.
it certainly works when the textview is inside a scrolled window.
I am encountering the same issue in Fedora 27 in UberWriter. Setting left- and right margin makes the textview expand, even though wrapping is set to word wrap. Same effect when setting a left padding in the CSS with the inspector. Any way I could help solve this bug?
(In reply to Timm Bäder from comment #2) > Created attachment 328418 [details] > Testcase > > This seems to happen whenever left-margin *and* right-margin are set. > Without the g_object_set call here, everything works fine. pedantry: as your test case showed, both are not required; the logic is that having either left *or* right margin will cause the problem.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/628.