Bug 88696 - Field text with no-break spaces in a table cell doesn't follow line break paragraph rules
Summary: Field text with no-break spaces in a table cell doesn't follow line break par...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Writer-Tables Paragraph
  Show dependency treegraph
Reported: 2015-01-22 09:05 UTC by Alexander Polkhovskiy
Modified: 2023-09-07 03:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Example with no-break spaces in fields in a cell (34.09 KB, application/vnd.oasis.opendocument.text)
2015-01-22 09:05 UTC, Alexander Polkhovskiy

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Polkhovskiy 2015-01-22 09:05:54 UTC
Created attachment 112648 [details]
Example with no-break spaces in fields in a cell

I have a paragraph style with no wordbreak. I.e. I want the text (<nbsp> - no-break space) "My<nbsp>verylongwordtext and his<nbsp>verylongtext" remain as it is. I uncheck all automatic word break options in the paragraph style options and type the text in a table cell. Everything works fine.
Then I put this text to a new field and paste this field in that table cell. I expect to see same result. But depending on the font height and cell width I see some words are splitted between lines without hyphens. For example, I get this:
"My<nbsp>verylongwordtext and his<nbsp>verylongt
instead of ths:
"My<nbsp>verylongwordtext and
If I replace no-break spaces with simple ones, works OK. If I use just plain text, not field, works OK.
I noticed, that it appeares not in first line.
Comment 1 Buovjaga 2015-01-29 18:53:30 UTC

I removed the words in the Whiteboard field, please see https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Whiteboard/Advanced

Win 7 Pro 64-bit Version:
Build ID: 784d069cc1d9f1d6e6a4e543a278376ab483d1eb
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-25_23:07:36

Ubuntu 14.10 64-bit
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-
Comment 2 QA Administrators 2016-02-21 08:38:21 UTC Comment hidden (obsolete)
Comment 3 Alexander Polkhovskiy 2016-02-24 06:34:42 UTC
I still see the bug in LO v x86
ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737
CPU Threads: 4; OS Version: Windows 6.2 (8.1) x64; UI Render: default; 
Locale: ru-RU (ru_RU)
Comment 4 QA Administrators 2017-03-06 16:13:58 UTC Comment hidden (obsolete)
Comment 5 Alexander Polkhovskiy 2017-03-07 08:17:59 UTC
Still present in LO v
ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1
Windows 6.2; Rendering: default;
Locale: ru-RU (ru_RU)
Windows 8.1 PRO x64
Comment 6 QA Administrators 2018-03-08 03:44:08 UTC Comment hidden (obsolete)
Comment 7 Alexander Polkhovskiy 2018-03-10 09:40:26 UTC
Still present in LO v
ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89
Windows 6.3; Rendering: default;
Locale: ru-RU (ru_RU)
Windows 8.1 PRO x64
Comment 8 QA Administrators 2019-09-03 16:11:10 UTC Comment hidden (obsolete)
Comment 9 Alexander Polkhovskiy 2019-09-04 08:26:47 UTC
Reproduced in 
Version: (x86)
Build ID: 2c7aa60b69967a80b7874503f0e9e85546a04cde
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-09-04_06:15:45
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: CL
Comment 10 QA Administrators 2021-09-04 04:02:05 UTC Comment hidden (obsolete)
Comment 11 Alexander Polkhovskiy 2021-09-06 18:39:53 UTC
Reproduced in
Version: (x64) / LibreOffice Community
Build ID: 3cfc32d9754d2d239bd8ce2941029c12873010c1
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win
Locale: ru-RU (ru_RU); UI: ru-RU
Calc: CL
Comment 12 QA Administrators 2023-09-07 03:15:54 UTC
Dear Alexander Polkhovskiy,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team