Description: On Windows 7 text in all cells are bit lower, than vertical center. When cell text is in edit mode, that text moves few pixels higher. After editing is done, text returns to previous position, which is still off vertical center. Steps to Reproduce: 1. Open new spreadsheet. 2. Enter some text. Actual Results: Entered text is few pixels lower, than it should be. When editing, text is a bit higher. Expected Results: Text should stay vertically centered at all times, except when special formatting is applied. Reproducible: Always User Profile Reset: Yes. Problem still exists in safe mode. Additional Info: Version: 5.3.0.3 (x64) Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; Locale: lt-LT (lt_LT); Calc: group User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0
Created attachment 131373 [details] Text alignment issue
Hi, Thanks for reporting. This is the expected behaviour and it has been like that since OpenOffice, thus this is considered as not a bug. Closing as RESOLVED NOTABUG
It was working "correctly" in LibreOffice 5.2, all text was neatly aligned in the middle vertically. I think it is a regression.
Created attachment 131389 [details] LibreOffice 5.2.5.1
Created attachment 131390 [details] LibreOffice 5.3.0.3
Please, take a look at two new screenshots, comparing similar views on 5.2 and 5.3 versions of LibreOffice. You will clearly see, that in 5.3 text is rendered a few pixels lower than in previous version.
This bug was never confirmed. Moving back to UNCONFIRMED
I'm sorry but I don't consider this a bug. It's true the vertical alignment is slightly different than in previous versions of LibreOffice, but it's not causing any side-effect, thus, we can consider this a bug.
When entering characters with carons (see attached screenshot) they are cut off, because all text is shifted upwards. This is a usability issue.
Created attachment 134419 [details] Character carons are cut off
Moving it back to UNCONFIRMED until someone else confirms it.
Repro the caret thing, but it already happens in 4.4.7.2. Not in 3.5, though. Unable to bibisect on Win as it does not go to 3.5, but I can also repro on Linux, so it could be bibisected. Win 10 Version: 5.4.0.3 (x64) Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c CPU threads: 4; OS: Windows 6.19; UI render: default; Locale: fi-FI (fi_FI); Calc: group Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.3 Build ID: 5.4.0-1 CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group
More testing: on Linux with 3.6.7.2, both Ř and Č are raised so the carets are cut off. With 3.3, the Č is by default so high that the caret is cut off. On Windows with 3.5.0, the Ř is raised, but caret is not cut off and Č does not move and is not too high. So I'm not sure, if bibisecting is worth it.
Bibisected on Linux with 43all, targeting as bad any build where the text moves when you start to edit it. Range given: https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=bed0447cefb949fc77cfde7543397d96590082ba...c29af1572ad15ac5199a09e5812fb8354c165329 Nothing jumps out to me. Take with a grain of salt or ignore.
Dear joshas, 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
While character vertical alignment issue is not so extreme in current version, but when editing characters move about 1px up in cell. Caron cut-off issue still exists. Default cell height could be about 2px higher to fix it. Version: 6.2.4.2 (x64) Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; Locale: lt-LT (lt_LT); UI-Language: en-US Calc: CL
Issue still occurs in LibreOffice 7.0.5.2 on Fedora 33. While uppercase characters carons are not cut off, it is still a bit annoying when text moves up after pressing F2 to edit it and moves down after pressing Enter.
Dear joshas, 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
LibreOffice Calc on Fedora Linux 37 (Workstation Edition) Version: 7.4.6.2 Build ID: 40(Build:2) CPU threads: 12; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: lt-LT (en_US.UTF-8); UI: en-US Calc: threaded Issue is still here, but text in edit mode moves up only by a single pixel, so character carets are not cut off and it is more of an annoyance than major blocker. It would be interesting to hear from technical perspective, why this issue happens. I'd guess that "text" and "edit" components have a bit different rendering rules?
I did another bibisect and looks like in 5.4 it got less severe due to 60eed46d4b24b9b9eaa1ebd0a8f185900176aed5 Resolves: tdf#107249 round ascent/descent/extleading on conversion to int
Adolfo, I included you here, if you can take a look.