Description: If open *.doc or *.docx documents and string on center or justify align then text cursor visual don't move with space on end string. Steps to Reproduce: 1. Open *.doc or *.docx documents. 2. Move text cursor on end string with align center or justify. 3. Press space one or more. Actual Results: Text cursor don't move with space on end string. Expected Results: Text cursor move with space on end string. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Created attachment 141552 [details] text cursor don't move with space
The visual problem here is that it's not visible where in the trailing spaces cursor is at the moment (it stays as if it's "in front of" the spaces, when actually it's in the middle or at the end); it's impossible to put cursor to a specific place inside this trailing space string using mouse; and the Paragraph mark is displaced visually. The feature to handle trailing spaces in Word-compatible way was introduced in bug 104668.
Removing keywords per Mike's comment on IRC
morphey008: When changing field values, please take a second to read the comment (in parentheses) in the field's label.
Dear morphey008, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still a problem in: Version: 7.2.0.0.alpha0+ (x64) Build ID: cb084f475db33a2cfc62bc9c8de37b8c3c87b3c7 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL Does not happen with a new empty document, or an odt one.
*** This bug has been marked as a duplicate of bug 120715 ***