Bug 122664 - Optimal Column Width wrong with certain magnifications (or fonts?) (regression)
Summary: Optimal Column Width wrong with certain magnifications (or fonts?) (regression)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.2.0.2 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
: 123513 (view as bug list)
Depends on:
Blocks: Kerning
  Show dependency tree / graph
 
Reported: 2019-01-12 00:00 UTC by Jim Avera
Modified: 2024-01-05 16:51 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:

Attachments
Demo spreadsheet (optwidthbug.ods). Pease see "Steps to Reproduce" (11.27 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-01-12 00:01 UTC, Jim Avera 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Avera 2019-01-12 00:00:44 UTC 
Description:
Setting "Optimal Column Width" with zero additional padding results in some numeric values showing as "###".   This happens in 6.2 and master, but not in  6.0.7.3.

Steps to Reproduce:
1. Open attached demo spreadsheet (optwidthbug.ods)
2. Click in header corner to select everything. 
3. In column headers, Rightclick->Optimal Width...
   Set the "Add:" amount to 0
   Click OK

Actual Results:
The numbers in Columns E,F, and G are displayed as "###".
(should be 112.60 112.61 and 112.60 respectively).

Expected Results:
Column width should be set correctly to display all cell contents without "###" overflow markers.


Reproducible: Always


User Profile Reset: No



Additional Info:
Problem is master, 6.2.1.0.0+, but not in  6.0.7.3
Comment 1 Jim Avera 2019-01-12 00:01:21 UTC 
Created attachment 148248 [details]
Demo spreadsheet (optwidthbug.ods).  Pease see "Steps to Reproduce"
Comment 2 raal 2019-01-12 08:19:41 UTC 
open the file is enough, I think.

This seems to have begun at the below commit.
Adding Cc: to Eike Rathke ; Could you possibly take a look at this one?
Thanks
 7f07e1b5cfeb5ca94b2410813a7b19bae986e3bf is the first bad commit
commit 7f07e1b5cfeb5ca94b2410813a7b19bae986e3bf
Author: Jenkins Build User <tdf@pollux.tdf>
Date:   Tue Jul 3 17:22:22 2018 +0200

    source 36eed54d3dfed6551fd2ad944feff7e217c56e82

author	Eike Rathke <erack@redhat.com>	2018-07-03 15:00:26 +0200
committer	Eike Rathke <erack@redhat.com>	2018-07-03 17:12:33 +0200
commit 36eed54d3dfed6551fd2ad944feff7e217c56e82 (patch)
tree 8db66cec37a3532157442bd256ab8c9fb24d806c
parent fb84f580025503673ba45684b7c18c41b27c2a06 (diff)
Resolves: tdf#118221 whole cell kerning default is off
Comment 3 Jim Avera 2019-12-17 20:40:11 UTC 
Hello, any progress on this?   It was a regression introduced almost a year ago.

Still broken in 6.5.0.0.alpha0+ master as of 2019-12-11.

Thanks...
Comment 4 Eike Rathke 2019-12-18 13:43:04 UTC 
I can reproduce, but I have no idea how to fix it.
Comment 5 Justin L 2021-11-23 17:33:10 UTC 
*** Bug 123513 has been marked as a duplicate of this bug. ***
Comment 6 Colin 2022-01-27 08:23:48 UTC 
(In reply to Eike Rathke from comment #4)
> I can reproduce, but I have no idea how to fix it.

Perhaps my report with sample for Bug 147015 may provide a little inspiration
Comment 7 Colin 2022-01-27 08:32:52 UTC 
(In reply to Colin from comment #6)
> (In reply to Eike Rathke from comment #4)
> > I can reproduce, but I have no idea how to fix it.
> 
> Perhaps my report with sample for Bug 147015 may provide a little inspiration

I can confirm that amending the pair kerning on the sample sheet for this bug 122664 will immediately reveal the valid numbers - not even necessary to re-optimise the column width.
Comment 8 Colin 2022-01-27 08:37:24 UTC 
(In reply to Colin from comment #7)
> (In reply to Colin from comment #6)
> > (In reply to Eike Rathke from comment #4)
> > > I can reproduce, but I have no idea how to fix it.
> > 
> > Perhaps my report with sample for Bug 147015 may provide a little inspiration
> 
> I can confirm that amending* the pair kerning on the sample sheet for this
> bug 122664 will immediately reveal the valid numbers - not even necessary to
> re-optimise the column width.

*Activating - no additional kerning values necessary
Comment 9 Caolán McNamara 2024-01-05 16:51:24 UTC 
Its possible that this is a duplicate of the issue fixed in bug 158997