If the red wave appears and the word in front of it is lengthened, for example, the red wave remains at its place even though the wrong word is shifted.
The "for example" shoud be in front of "the word in front...".
Thank you for reporting the bug. Please attach a sample document (or a before and after image) of the bug you are encountering, as this makes it easier for us to verify the bug. I believe I understand how to replicate the bug, but I would like to clarify the details surrounding your bug report before proceeding. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once a sample document or images is/are provided. (Note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for further details.)
Created attachment 157951 [details] This is befor.
Created attachment 157952 [details] Befor..
Sorry for doubeling..
Created attachment 157953 [details] ...and after
Thank you for providing additional information. I can confirm the bug is present in a recent master build in Windows and in the version described in the report. For the master build details: Version: 7.0.0.0.alpha0+ (x64) Build ID: e8ac78d3afdeb0302eaea34a50f1ca912d5fe897 CPU threads: 2; OS: Windows 10.0 Build 17763; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL I have escalated the severity of the bug to "trivial", as this is not an enhancement.
Dear bugzillalaaaal, 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
Still repro in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: b438854a0b5148880e455cbeeff14d4e3d825711 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL Jumbo