Description: In Table Properties | Text Flow, Break is a checkbox, with radio box options for whether the break should be a page or column break and before/after arranged like this: * Page * Column * Before * After That is unintuitive IMO. The large space between Page/Column and Before/After makes it look like Page and Before are the grouped options and Column/After are the grouped options. A more intuitive layout would be: * Page * Before * Column * After Moreover, this is totally inconsistent with how the options are displayed in Format | Paragraph | Text Flow. In that menu, Breaks is a separate menu with a checkbox for Insert, and drop down menus for Type (Page/Column) and Position (Before/After). Common to both is that "With Page Style" is a checkbox with a dropdown menu and "Page Number" is also a checkbox with a scroll menu, albeit arranged vertically in the Paragraph Text Flow menu but horizontally in the Table Text Flow menu. IMO, these Text Flow windows should be made consistent with each other, with the Paragraph Text Flow menu -- which is arranged logically and intuitively -- serving as the basis. The option should be a checkbox named either Break or Insert in both menus, and the Table Properties Text Flow window should have Type and Position as separate drop down menus, and all menus should be on their own line (Type, Position, With Page Style, Page Number) just like in the Paragraph Text Flow menu. Steps to Reproduce: 1. Create a Table. Go to Table Properties | Text Flow. See the arrangement of the break options. 2. Go to Format | Paragraph | Text Flow. Compare the arrangement of the break options there. Actual Results: Menus are inconsistent. Expected Results: Menus should be consistent. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.6.3 (X86_64) / LibreOffice Community Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Proposed solution in bug 151002 *** This bug has been marked as a duplicate of bug 151002 ***