Bug 88283 - Calc - Fill vertically exceeds top of cell boundary by 1px greater than No Fill cells
Summary: Calc - Fill vertically exceeds top of cell boundary by 1px greater than No Fi...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.3.5.2 release
Hardware: All All
: lowest minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-11 00:28 UTC by Marc Meledandri
Modified: 2019-12-16 18:08 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
testcase (9.23 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-01-11 00:28 UTC, Marc Meledandri
Details
Testcase-Proper-Mime-Type (9.23 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-01-11 00:30 UTC, Marc Meledandri
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Meledandri 2015-01-11 00:28:50 UTC
Created attachment 112079 [details]
testcase

STR:

1) Fill area with any color
2) Select No Fill for a horizontally adjacent cell
3) Notice vertical alignment mismatch between filled and non-filled cells

Please see simple testcase attachement
Comment 1 Marc Meledandri 2015-01-11 00:30:14 UTC
Created attachment 112080 [details]
Testcase-Proper-Mime-Type
Comment 2 Marc Meledandri 2015-01-11 15:23:05 UTC
I'm not sure what the indended behavior is, only that filled and No Filled cells don't align.

I suppose the converse of my summary could be true:
Perhaps No Fill should be removing one more row of pixels at the top edge of a cell. That would also fix this problem,
Comment 3 raal 2015-01-12 11:52:32 UTC
I can confirm with LO 4.3.5, win7.

This also exists in excel, so probably not a bug. Leaving unconfirmed.
Comment 4 Joel Madero 2015-10-17 17:13:56 UTC
Hi Marc,

I'm going to go ahead and push this to NEW - it does indeed seem a little strange (even if Excel behaves the same). 

That being said:
New
Minor - not going to prevent high quality work at all;
Lowest - not going to impact a lot of users at all, I can't imagine many case scenarios where this would actually be an issue. Also, Excel behaving the same way gives some weight to the "users don't care" or "users don't notice" or "users have learned to work around it" - all of which contribute to my assessment that this is a really minor issue.
Comment 5 QA Administrators 2016-11-08 11:42:17 UTC Comment hidden (obsolete)
Comment 6 Marc Meledandri 2016-12-11 17:12:14 UTC
The original STR as reported and shown in comment 1 attachment can be still be reproduced in Version: 5.1.6.2.
Comment 7 QA Administrators 2017-12-13 09:30:00 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2019-12-14 03:41:16 UTC Comment hidden (obsolete)
Comment 9 Marc Meledandri 2019-12-16 18:08:25 UTC
This bug is still present in versions 6.2.8 and 6.3.4.

Version: 6.3.4.2
Build ID: 60da17e045e08f1793c57c00ba83cdfce946d0aa
CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded