Bug 52203 - Cell-Borders FORMATTING: the same width lines displayed differently
Summary: Cell-Borders FORMATTING: the same width lines displayed differently
Status: RESOLVED DUPLICATE of bug 51178
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.6.0.1 rc
Hardware: Other macOS (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-17 14:58 UTC by Johannes Weberhofer
Modified: 2013-03-07 17:04 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example document looking strange in 3.6.0rc1 (8.15 KB, application/vnd.oasis.opendocument.spreadsheet)
2012-07-17 14:58 UTC, Johannes Weberhofer
Details
All lines should have the same width (7.23 KB, image/png)
2012-07-17 14:59 UTC, Johannes Weberhofer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Weberhofer 2012-07-17 14:58:57 UTC
Created attachment 64318 [details]
Example document looking strange in 3.6.0rc1

Table-Borders having the same width are displayed correctly with v3.5.4 but are looking strange in the 3.6.0rc1 (OSX) and on a 3.5.4.7 (Opensuse 12.1).
Comment 1 Johannes Weberhofer 2012-07-17 14:59:46 UTC
Created attachment 64319 [details]
All lines should have the same width
Comment 2 Rainer Bielefeld Retired 2012-07-17 15:52:04 UTC
This one is a DUP of "Bug 51178 - FILEOPEN document from older version: borders width around conditional formatted cells looks thicher than when opened with old version"

It's not easy to find out existing formatting with our Dialog, it' only designed to transfer data to the Cells, but not to find out formatting data. So I deleted all superfluous cell formatting, only border between row 1 and row 2 remain. Now you see that the dividing border does NOT have same thickness anywhere, but:

- A1:A2, C1:C2 width 0,50pt
- B1:B2              0,05pt

This difference was not visible in older versions.

For more details please see Bug 51178

*** This bug has been marked as a duplicate of bug 51178 ***