Bug 115849 - Allow table to split across pages and columns enabled when adding row
Summary: Allow table to split across pages and columns enabled when adding row
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.1.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, needUITest, regression
Depends on:
Blocks: Cell-Add-Delete
  Show dependency treegraph
 
Reported: 2018-02-19 12:48 UTC by Pascal Becker
Modified: 2019-03-15 07:04 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Becker 2018-02-19 12:48:16 UTC
If "Allow table to split across pages and columns" is disabled for table and a new row is added, then "Allow table to split across pages and columns" is automatically enabled again.

1. Create a table
2. Open table properties and disable "Allow table to split across pages and columns"
3. Commit with "OK"
4. Table behaves corretly and does not split at page the end of the page
5. Add a new row to the table
6. Table splits at page the end of the page
7. Open table properties. The option "Allow table to split across pages and columns" is enabled again.
Comment 1 Dieter Praas 2018-02-20 08:36:06 UTC
Reproducible 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



But not in 

Version: 5.4.5.1 (x64)
Build-ID: 79c9829dd5d8054ec39a82dc51cd9eff340dbee8
CPU-Threads: 4; BS: Windows 6.19; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group
Comment 2 IWAMOTO 2018-02-20 09:08:02 UTC
This was reproduced in the following environment.

Version: 6.0.1.1 (x64)
Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6
Locale: ja-JP (ja_JP); 
OS:Winsows7 Home Premium x64
CPU:Intel(R)celeron(R)2.00GHz
Comment 3 Xisco Faulí 2018-02-23 13:34:19 UTC
Regression introduced by:

author	Jim Raykowski <raykowj@gmail.com>	2017-10-31 15:48:07 -0800
committer	Miklos Vajna <vmiklos@collabora.co.uk>	2017-12-20 09:11:47 +0100
commit	416f7578d6332b5b5a4445f26307d73925188e41 (patch)
tree	c84e21fe1b096f149baf03a95bce82f5b385ad2e
parent	226804c8f7d2306562380283edfd919a88863807 (diff)
tdf#107555 Apply 'Default Style' table style to newly inserted tables

Bisected with: bibisect-linux64-6.1

Adding Cc: to Jim Raykowski
Comment 4 Jim Raykowski 2018-02-24 02:11:58 UTC
This can be recreated in previous versions by

1. insert table Ctrl-F12
2. apply table style Menu > Table > AutoFormat Styles...
3. continue at step 2 using Pascal's instructions

This happens because an AutoFormat Style is applied to the table. This was introduced in 
tdf#107555 Apply 'Default Style' table style to newly inserted tables

This should be reverted along with 
tdf#108227 Set table style so it is highlighted in Sidebar styles list 

For the moment, one way to remedy this is 

1. insert tables using Menu > Table > Insert Table... or Ctrl-F12
2. click on AutoFormat button
AutoFormat dialog appears and 'None' should be highlighted in the Format list box 
3. click OK
4. click OK to insert the table
Comment 5 QA Administrators 2019-03-15 03:55:24 UTC Comment hidden (obsolete)
Comment 6 Pascal Becker 2019-03-15 07:04:51 UTC
Just tested it in Version 6.2.2.1 and the bug still persists.

Version: 6.2.2.1 (x64)
Build-ID: fcd633fb1bf21b0a99c9acb3ad6e526437947b01
CPU-Threads: 8; BS: Windows 10.0; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: CL