Problem description: If font size 10 is zoomed to 66% (or font size reduced to 7 at 100%), the minimum height split pane is two rows rather than one row (column headers). A. Tried split after zoom 66% Steps to reproduce: 1. New Spreadsheet (default font size is 10) 2. Reduce zoom level to 66% (lower right slider) 3. Add 1 column header row and some data under them 4. Drag split pane button (above right scroll bar) and try to split pane so top pane shows only column headers. Current behavior: Minimum top pane height is 2 rows. Expected behavior: Minimum top pane height is height of a text line in row 1 (at current zoom level and font). B. Tried split after reduce font size to 7 Changing the font size to 7 at 100% zoom does not not help, still shows a minimum of two rows in the top header pane. 5. return zoom to 100% 6. click in a cell, type control-A to select all cells 7. Reduce font size from 10 to 7. 8. Try to reduce split pane height to 1 row. Current Behavior: Minimum height is 2 rows. Expected Behavior: Minimum height is 1 row at current font level. C. Tried with double click split button Double click pane splitter removes split pane. So I expected that double clicking split button (above right scroll bar) would add a split pane, maybe at minimum height. 1. new sheet 2. double click split button (above right scroll bar) Current Behavior: Nothing happens Expected Behavior: Split sheet, maybe at minimum height. It did not split pane (on a new sheet). I guess it remembers previous split. If there is no previous split, then maybe the default could be 1 row split instead of no split. p.s. Thank you for your work!
Can you attach a file or a screen please. i try reproduce your problem in 4.0.2.2 and the dealy master but i can't. I want see what happens in your LO.
Created attachment 77716 [details] Libre Office Calc 4.0.2.2 cannot make 1 frozen row at 65% Thanks for looking at this. I just tried again with 4.0.2.2. Clicked the zoom '-' button 4 times to get 65%. It looks like now if I drag down to 2 rows, then it always snaps to an integer number of rows (2 rows, 3 rows, etc.) and I cannot drag it up to 1 row. But if I start over from no frozen rows and drag slowly, I may be able to get it to drag to 1.3 rows or so (not an integer), but not 1 row. It is not obvious why the behavior is different (continuous fractional number of rows vs. snap to integer row sizes).
Please, do not report several different problem in the same bug report, instead file a new bug report for each one. I do not reproduce the problem A with LibreOffice 4.0.4.0+ under Ubuntu 12.04 x86-64 (Build ID: 243df043a4ee78509049c5fd5a9f72cce46b029), nor with current release 4.0.2.2 (Build ID: 4c82dcdd6efcd48b1d8bba66bfe1989deee49c3) Best regards. JBF
I have been able to confirm the issue on: Version 3.6.5.2 Platform: Bodhi Linux 2.2 x64 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + As I've been able to confirm this problem on an earlier release I am changing the version number as version is the earliest version that we can confirm the bug, we use comments to say that the bug exists in newer versions as well. Marking as: New (confirmed) Minor - does not prevent high quality work, may slow it down just a little (but probably not even this) Low - default for minor bugs, seems appropriat Keywords - Whiteboard Status - ProposedEasyHack + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
I can confirm that all problems A,B,C on the Description not reproducible using LO 4.0.3.3 (Win7 32bit) Perhaps problems has been fixed. Change status to RESOLVED WORKSFORME ?
Per comment marking as WFM. @gekacheka - if this is not the case on latest stable please mark bug as UNCONFIRMED again (probably need to mark as NEEDINFO then UNCONFIRMED due to limits with bug tracker) and provide any additional info requested. Thanks all!
As of Version 4.0.3.3 (Build ID: 0eaa50a932c8f2199a615e1eb30f7ac74279539) it is still behaving as originally reported. Windows XP sp3, 1280x800 screen, 96dpi, font is Arial 10.
still not happen on LO 4.0.4.1 (Win7 32bit), 1280x768 screen, 96dpi spesific to XP?
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval. Thank you and apologies for the noise
I reproduce A. Don't repro B. Win 7 64-bit dev build Version: 4.4.0.0.alpha1+ Build ID: 14a2cfc27f86112469f2a2252bdc154ad8d3219f TinderBox: Win-x86@42, Branch:master, Time: 2014-10-28_04:51:26
Migrating Whiteboard tags to Keywords: (needsDevEval) [NinjaEdit]
** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Issue A is still reproducible. If zoom level is small, it isn't possible to have only one row in the top split view. Issue C and B not reproducible. Version: 6.2.0.0.alpha1+ Build ID: fff34169fa912ad5096f1652172ea2455e5cb4d3 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: threaded
Dear gekacheka, 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 gekacheka, 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
In 7.6.4.1, is possible to get 1 row split using steps A or B. It may take a little mouse dragging to get the height just right to show only 1 row, but it is possible. Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded