Bug 112937 - Line break doesn't work if there is a non-standard space before the closing bracket and and between the closing bracket and slash.
Summary: Line break doesn't work if there is a non-standard space before the closing b...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.8.2 release
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Formatting-Mark Paragraph
  Show dependency tree / graph
 
Reported: 2017-10-06 14:41 UTC by t0m1p
Modified: 2025-01-16 03:12 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Non-standard spaces (31.32 KB, application/vnd.oasis.opendocument.text)
2017-10-06 14:43 UTC, t0m1p 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description t0m1p 2017-10-06 14:41:26 UTC 
Description:
Inserting various non-standard (Unicode) spaces in the attachment won't allow the line to break at the position where the space was inserted if it's immediately before the closing bracket or between the closing bracket and slash. 

Steps to Reproduce:
1. Have a look at the attachment

Actual Results:  
The line will not break if a non-standard space is immediately before the closing bracket or between the closing bracket and slash. 

Expected Results:
The line should break at the non-standard space inserted immediately before the closing bracket or between the closing bracket and slash as well. 


Reproducible: Always

User Profile Reset: Yes

Additional Info:
I actually found the bug when pasting ZWSP to allow line break between the closing bracket and slash. 


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
Comment 1 t0m1p 2017-10-06 14:43:18 UTC 
Created attachment 136805 [details]
Non-standard spaces
Comment 2 Dieter 2017-10-06 15:45:29 UTC 
Did you test it with an actual version? If not, could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 3 t0m1p 2017-10-09 15:17:38 UTC 
The bug is present in the latest version as well, what other info do you need? 

Is the attachment OK?
Comment 4 Buovjaga 2017-11-04 17:40:31 UTC 
So what are we testing here? Do you want us to try and insert a paragraph or line break at these positions you are talking about? It seems to work fine here.
Comment 5 t0m1p 2017-11-04 18:44:54 UTC 
When I insert e.g. ZWSP immediately after the closing bracket, the line is allowed to break when the part after the ZWSP is too long, as if it was a standard space. That's OK. 

On the other hand, when I insert the same type of space immediately before the closing bracket, the line is not allowed to break when the part after the ZWSP is too long, which is the same as if there wasn't any space. That's not OK.
Comment 6 Buovjaga 2017-11-04 19:01:19 UTC 
By "line", are you referring to the multiple underscores in your file?
Comment 7 t0m1p 2017-11-04 19:11:07 UTC 
Yes, mostly. My "line" is any series of non-newline characters. 

The thing is, that the left and right column should be almost the same (as it is the case for standard space, see "SPACE"). That is, there should be no difference between inserting a special space before or after the bracket.
Comment 8 Buovjaga 2017-11-04 19:17:07 UTC 
Ok, let's set to NEW
Comment 9 QA Administrators 2019-09-03 16:11:27 UTC Comment hidden (obsolete)
Comment 10 t0m1p 2023-01-16 10:12:59 UTC 
Zero width space is the only one that works everywhere.
No other space between the closing bracket and slash works. 
All spaces immediately after the closing bracket and slash now work. 

Tested on:
Version: 7.4.2.3 / LibreOffice Community
Build ID: 40(Build:3)
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb)
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Ubuntu package version: 1:7.4.2~rc3-0ubuntu1
Calc: threaded
Comment 11 QA Administrators 2025-01-16 03:12:36 UTC 
Dear t0m1p,

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

MassPing-UntouchedBug