Bug 90084 - TABLE: Inserting rows/columns to single row/column table does not default to having inner cell lines
Summary: TABLE: Inserting rows/columns to single row/column table does not default to...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) All
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 105509 (view as bug list)
Depends on:
Blocks: Table-Borders
  Show dependency treegraph
 
Reported: 2015-03-18 13:51 UTC by Gordo
Modified: 2022-11-16 03:46 UTC (History)
2 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 Gordo 2015-03-18 13:51:35 UTC
1. New Text Document.
2. Table -> Insert Table.
3. Set 2 columns and 1 row and Insert.
4. Place cursor inside table.
5. Table -> Insert -> Rows.
6. Choose 1 and OK.
Expected Result:
There is a horizontal line between row 1 and 2.
Result:
No horizontal line between row 1 and 2.

From the Writers Guide:
The default table has thin black borders around each cell (grid).

While it is visually true for a one row or one column table, I get it that in that instance there are no adjoining cells hence no borders.  Inserting rows or columns should default to having inner lines if no other border formatting has been set.

Version: 4.4.1.2
Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Comment 1 A (Andy) 2015-03-18 16:55:51 UTC
Reproducible with LO 4.4.1.2, Win 8.1
Comment 2 tommy27 2016-04-16 07:28:38 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2017-05-22 13:26:49 UTC Comment hidden (obsolete)
Comment 4 Roman Kuznetsov 2019-02-01 20:30:46 UTC
still repro in

Version: 6.1.4.2
Build ID: 1:6.1.4-0ubuntu0.18.10.1
CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
Locale: ru-RU (ru_RU.UTF-8); Calc: group threaded
Comment 5 Telesto 2020-11-15 10:58:59 UTC
*** Bug 105509 has been marked as a duplicate of this bug. ***
Comment 6 QA Administrators 2022-11-16 03:46:47 UTC
Dear Gordo,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug