GNOME Bugzilla – Bug 345861
col/row auto-sizing ignores merged regions with 1 col/row
Last modified: 2018-05-22 13:16:37 UTC
Please describe the problem: If you resize a row by doubleclicking on a line separating two rows the resulting row size will be too small. I.e. not big enoough to be able to display all lines withing a cell inside such a row. Steps to reproduce: 1. load the attached gnumeric sheet 2. double-click on the line separating the "1" and "2" widgets Actual results: The first row is resized too small, so that you can't read the second line in the cell. Expected results: The row should be resized in a way so that all the text inside the cell can be read. (Something like: size_of_row = number_of_lines * size_of_line + border_size) Does this happen every time? yes Other information: See gnumeric sheet at http://sourcepole.ch/tpo/tmp/kak.gnumeric
Created attachment 67969 [details] gnumeric sheet that displays the faultybehaveour
I've also attached the gnumeric sheet that displays the faulty behaveour
First of all, both cells contain only single lines of text. So all lines are being shown. The behaviour in your sample file is correct. If you switch on "wrap text" (see Format Cell/Alignment) double clicking should work as you expect. It turns out that it doesn't. That is a side effect of the merge cell (and is clearly a bug). If you unmerge the cell the behaviour is correct.
- The sample provided is correct. Without wrap-text enabled in A1 the content will not wrap to a new line, and auto-height calculation is correct. - With wrap-text on we are currently using XL behavior and ignoring the merged cell during calculations. However, I'm inclined to agree with Andreas that this violates the principle of least surprise. This seems like a valid special case. It would get too complex to handle merges with > 1 row for height, or > 1 col for width, but here it should be doable.
*** Bug 710205 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnumeric/issues/60.