Do the following: a. File>New>Spreadsheet b. Select all cells c. Format>Columns>Optimal Width enter 0 in Add, unselect Default value [OK] d. Enter 1 in cell A1 e. Select column A, double-click right column separator in column A. f. Column width changes to .53cm g. Format>Columns>Optimal Width Add still shows 0, just do [OK] h. Column width changes to .33cm The correct column width value is at step h: the value at step f is that with the default add value of 2mm, rather than the correct value of 0. Same result in safe mode. Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded
(In reply to David Lynch from comment #0) > Do the following: > a. File>New>Spreadsheet > b. Select all cells > c. Format>Columns>Optimal Width enter 0 in Add, unselect Default value [OK] > d. Enter 1 in cell A1 > e. Select column A, double-click right column separator in column A. > f. Column width changes to .53cm > g. Format>Columns>Optimal Width Add still shows 0, just do [OK] > h. Column width changes to .33cm > > The correct column width value is at step h: the value at step f is that > with the default add value of 2mm, rather than the correct value of 0. I don't understand what you mean. The resulting width in step f depends on the content of the selected cells (cell A1 in this case) for step e. So I don't see how the width of the column in step f would result in some specific expected value (which would be incorrect in Calc according to your description in comment 0?) Additionally, the width also depends on other factors, such as the size of the font and the zoom value.
I agree that the width in step f depends on the contents of selected cells. Call this width x. If A1="1", x=.53. Step g should do nothing, all it does is invoke the Optimal width dialog, change nothing and close the dialog. Yet the column width in step h changes to x-.2cm. If I enter w in cell A1, x=.59cm, and the width at step h changes to .39cm=x-.2cm.
(In reply to David Lynch from comment #0) > Do the following: > a. File>New>Spreadsheet > b. Select all cells > c. Format>Columns>Optimal Width enter 0 in Add, unselect Default value [OK] > d. Enter 1 in cell A1 > e. Select column A, double-click right column separator in column A. > f. Column width changes to .53cm I get .50 cm > g. Format>Columns>Optimal Width Add still shows 0, just do [OK] > h. Column width changes to .33cm I get .30 cm. So I still reproduce as described: double-click on column header boundary results in an optimal width of minimal + 2 mm. The same happens in OOo 3.3. It's true the documentation doesn't say the two actions (dialog or double-click boundary) are disconnected: https://help.libreoffice.org/7.6/en-US/text/scalc/01/05040200.html UX/Design team, is this expected, or should the double-click use the latest "Add" value? In my opinion, it makes sense to make uniform, and allow users to set the Add value to then directly reuse it with the faster double-click method. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 40617d867346956588ac023511f31210107217f4 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
(In reply to Stéphane Guillou (stragu) from comment #3) > UX/Design team, is this expected, or should the double-click use the latest > "Add" value? No idea, it's rather a question to the developers. Btw, the last value is slightly below 0.3cm since okaying the optimal width dialog enlarges the column. (In reply to Stéphane Guillou (stragu) from comment #3) > In my opinion, it makes sense to make uniform... I struggle with the need to add something to the _optimum_. It makes the whole function hard to understand. But clearly one could expect the double-click method being the same function as the optimal width command.
Dear David Lynch, 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
Bug still present: Version: 25.8.4.2 (X86_64) Build ID: 290daaa01b999472f0c7a3890eb6a550fd74c6df CPU threads: 12; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL threaded