Bug 115537

Summary:	Unexpected table border when Box List table style is changed and then changed back
Product:	LibreOffice	Reporter:	Jim Raykowski <raykowj>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	dgp-mail, xiscofauli
Priority:	medium
Version:	6.1.0.0.alpha0+
Hardware:	All
OS:	All
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	107553

Description Jim Raykowski 2018-02-08 07:04:23 UTC

Here are the steps to repro:

1) open a new writer document
2) insert a table (Menu > Table > Insert Table or Ctrl-F12)
Insert Table Dialog opens
3) click on AutoFormat button
AutoFormat Dialog opens
4) click on Box List Blue
5) uncheck Borders checkbox
6) click on OK
7) click on Insert
Table with Box List Blue style is inserted in document
8) open the Sidebar Styles Deck
9) click on the Table Styles icon (6th icon left to right above the content list)
10) double click on Box List Green
Table changes style to Box List Green
11) double click on Box List Blue

Result: Table changes style to Box List Blue but borders remain set to Box List Green style

Expected result: Table changes style to Box List Blue with no borders

This happens with the all of the Box List table styles when the border is unchecked.

Comment 1 Dieter 2018-02-08 19:27:58 UTC

Reproducible for me with

Version: 6.1.0.0.alpha0+ (x64)
Build ID: 77a535285f0fd5f2464430abdc67cf99be024868
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-01-23_23:04:23
Locale: de-DE (de_DE); Calc: CL

Comment 2 QA Administrators 2019-02-09 03:44:50 UTC Comment hidden (obsolete)

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

Comment 3 Jim Raykowski 2019-02-09 08:43:59 UTC

Insert Table dialog has been reworked which has eliminated this bug.

Tested with:

Version: 6.3.0.0.alpha0+
Build ID: ee3cf6c82747385a1466cde66598d8e92859c904
CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

Comment 4 Xisco Faulí 2019-02-11 15:25:04 UTC

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.