Description: If a placeholder is formatted with a font that goes beyond the graphical boundaries of the placeholder box, and you replace i.e. remove the placeholder, then screen redrawling is incorrect. See screenshots. Turning hardware acceleration on or off doesn't change the outcome. Actual Results: Redrawing artifacts left. Expected Results: Clean redraw. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0 Cyberfox/50.0
Created attachment 130734 [details] Screen before placeholder removal
Created attachment 130735 [details] Screen after placeholder removal
Please attach an example document with the situation before removing the placeholder. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Actually, one does not even need a placeholder. It happens with any font with very long underlengths. Unfortunately, the font I use is proprietary, therefor, I can't attach it. Does anyone know a free font with very long underlengths?
(In reply to Patrick Schönbach from comment #4) > Unfortunately, the font I use is proprietary, therefor, I can't attach it. > Does anyone know a free font with very long underlengths? Maybe this: http://www.fontspace.com/jonathan-s-harris/signatures Here is the promising category: http://www.fontspace.com/category/thin,tall Could you please test, if you can reproduce the problem with some of those free ones?
Got it. Do the following: 1. Install the attached font "Signatures". 2. Open an empty Writer document. 3. Select font "Signatures", point size 32. 4. Type "gggggggggggg" -> LOWER PART OF LETTERS IS NOT DRAWN. 5. Prees Backspace -> LOWER PART OF LETTERS IS NOT ERASED.
Created attachment 130877 [details] Test font "Signatures"
(In reply to Patrick Schönbach from comment #6) > Got it. Do the following: > > 1. Install the attached font "Signatures". > > 2. Open an empty Writer document. > > 3. Select font "Signatures", point size 32. > > 4. Type "gggggggggggg" -> LOWER PART OF LETTERS IS NOT DRAWN. > > 5. Prees Backspace -> LOWER PART OF LETTERS IS NOT ERASED. Ok, I can reproduce. Step 5. depends on zoom level. Also, the problems disappear after you zoom out or in. No problem in version 3.6.7.2 Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: b12823aa81003e80372bd89db79bd6ba8e032a95 CPU Threads: 8; OS Version: Linux 4.9; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on February 1st 2016 Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.5.1 Build ID: 5.2.5-1 CPU Threads: 8; OS Version: Linux 4.9; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group
Created attachment 132038 [details] metrics for the Signatures font used for test font @Khaled, * So metrics for the test font here have the WinDescent set different than the hhea Descender and we look to be clipping to the hhea Descender on text entry. And, if I set the hhea Descender to match the WinDescent value the glyphs are fully formed on entry to canvas and when rubbed out with back space. So this is just bad font metrics, right? But then what is happening when zooming in or out to refresh the canvas? Why are the full glyphs showing on canvas--are different metrics (WinAscent/WinDescent rather than the hhea values) in use when zooming than when entering text?
Was testing on Windows 10 Pro 64-bit en-US with Version: 5.4.0.0.alpha0+ Build ID: f2efe33f71a8c092a19e3a27a85ac9057ebdca64 CPU threads: 8; OS: Windows 6.19; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2017-03-18_00:11:52 Locale: en-US (en_US); Calc: CL and with attachment 130877 [details] test font "Signatures" installed. The screen clip of its font metrics was with Type light (ver 3.2.037) freeware. =-ref-= http://cr8software.net/typelight.html
I don’t know for sure, but probably we are wrongly clipping on the typographic metrics rather than the clipping ones. Is this Windows/OpenGL only issue?
(In reply to Khaled Hosny from comment #11) > I don’t know for sure, but probably we are wrongly clipping on the > typographic metrics rather than the clipping ones. Is this Windows/OpenGL > only issue? I have only checked on Windows builds thus far, but it behaves the same on canvas with OpenGL, and Default and also without GPU acceleration. In initial QA confirmation @Buovjaga did show it as affecting Linux builds with default rendering.
** Please read this message in its entirety before responding ** 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 present in version 6.0.2.1
Windows 5.3 repo blames https://cgit.freedesktop.org/libreoffice/core/commit/?id=34d7602954d4483b3bc9db700e7df2c15348947a tdf#55469 Consistent line spacing across platforms
Dear Patrick Schönbach, 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
Dear Patrick Schönbach, 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://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
This bug was fixed as a part of fixing bug 152024, in the following commit: > https://git.libreoffice.org/core/commit/976b16b1c6ad6e6eaded7a9fb24388c4512e21e2 > > tdf#152024 Diacritics cut off at top and bottom of paragraph > > It will be available in 24.8.0. > > The patch should be included in the daily builds available at > https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More > information about daily builds can be found at: > https://wiki.documentfoundation.org/Testing_Daily_Builds > > Affected users are encouraged to test the fix and report feedback. Testing manually by following the instructions in comment 6, without the linked patch the bottom part of the 'g' character is truncated, but with the patch the full character is rendered as expected.