Bug 63729

Summary: PRINTING: UI: Table border rendered without antialiasing in Page preview
Product: LibreOffice Reporter: Milan Vančura <milan>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: barta
Priority: medium    
Version: 4.0.2.2 release   
Hardware: Other   
OS: All   
Whiteboard: BSA
Crash report or crash signature: Regression By:
Attachments: Page preview screenshot from CALC
Comparision of writer and calc table border in writer's Page preview
calc document showing the first problem
writer document showing problem from comment #1

Description Milan Vančura 2013-04-19 13:23:37 UTC
Created attachment 78237 [details]
Page preview screenshot from CALC

Problem description: 

Steps to reproduce:
1. create a table with a border and set border width, for example, to 1.55 pt on all 4 sides
2. go to File -> Page preview and look that the border thickness


Current behavior:

1. Border thickness differs on each side of the table.
2. If you change the document scale by the slider in the toolbar, table border
changes differently on each side of the table

I see fonts are with antialiasing but borders not. Probably this is the problem.
See the attached screenshot.

Expected behavior:

Border of same width looks as of same width.


Operating System: All
Version: 4.0.2.2 release
Comment 1 Milan Vančura 2013-04-19 13:28:05 UTC
Created attachment 78238 [details]
Comparision of writer and calc table border in writer's Page preview

As a comparision, I attach a screenshot of Page preview in writer, of a document containing two tables: first one done in writer and second one ctrl-C;ctrl-V from calc. You can see borders antialiased correctly  in writer's table and incorrecly in calc's table, both at the same time.

I do not know about code of Page preview sharing between writer and calc (GUI is slightly different) but it looks calc tables have problems in both previews.
Comment 2 Jan Holesovsky 2013-04-19 17:17:50 UTC
Milan: Thanks for reporting!  Can you please attach the example document so that everyone does not have to re-create it? ;-)
Comment 3 Milan Vančura 2013-04-19 18:56:20 UTC
Created attachment 78252 [details]
calc document showing the first problem
Comment 4 Milan Vančura 2013-04-19 18:58:37 UTC
Created attachment 78253 [details]
writer document showing problem from comment #1

There are both documents. It's a question if they show the same bug or a different ones because I see bad border width of calc table in writer document even under big magnification where it can't be an antialiasing problem.
Comment 5 QA Administrators 2014-05-17 00:34:08 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 6 QA Administrators 2014-06-01 20:30:07 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO